[SOLVED] Win10x64 Pro - Problems with SFC and DISM (605, 0x800f0900)

H

Hedini

Contributor
Joined
May 8, 2018
Posts
38
Hello,

something very strange happened this morning as my computer totally refuses to boot the standard Win 10 x64 Pro partition. Yesterday everything was fine, I turned it off and this morning the blue Windows logo appeared with the spinning circle as usual, then the logo disappeared and the circle stayed. That's all my PC does right now. After some tries I managed to start the recovery partition (that Win 10 PE) and both SFC and DISM did not work so far to fix my PC.

Maybe I am doing something wrong, but here is a bunch of logfiles which I got.

Again, I have no access to my installation, nor any safe-mode. Just that recovery partition and a command prompt, so I can't even run sfcfix.exe and that Windows-icon for "automatic repair" tells me that it could not fix the problem. :huh:
Luckily I can transfer files using a USB-drive and have a working Win10 Home notebook.

sfc.txt
sfc /scannow /offbootdir=f:\ /offwindir=f:\windows /offlogfile=e:\logfiles\sfc.txt
exits with "Windows Resource Protection could not perform the requested operation"


dism-analyze.txt
dism /image:f:\ /scratchdir:f:\temp /cleanup-image /analyzecomponentstore
exits with "0x800f0900 - DISM failed. No operation was performed."

dism /image:f:\ /scratchdir:f:\temp /cleanup-image /checkhealth
Tells me that the component store can be repaired.

dism-scan.txt
dism /image:f:\ /scratchdir:f:\temp /cleanup-image /scanhealth
exits with "605 - The specified buffer contains ill-formed data."

dism-restore.txt
dism /image:f:\ /scratchdir:f:\temp /cleanup-image /restorehealth
exits with "605 - The specified buffer contains ill-formed data."

I'd really like to know what happened here as I never saw such behavior before... :noidea:
Can somebody help me, or do I have to reinstall Windows?


Kind regards,
Chris

View attachment dism-analyze.zip
View attachment dism-restore.zip
View attachment dism-scan.zip
View attachment sfc.zip
 
Hello and welcome to Sysnative! Let's see if we can get you booted up.

Step#1 - FRST Scan

1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.

2. Copy it to your USB drive.
3. Boot to recovery environment.
4. Launch CMD and launch FRST64.exe from the USB.
5. Press Scan button.
6. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the USB)
7. Please attach the log back here.


Please note that there is no guarantee that I will be able to help you, but I will try.
 
Alright. It is very late, so we will continue after I get home from work later today.

In the meantime, do this:

Download the attached file fix.zip. Extract it to the root of your USB drive along with the fixlist.txt and repeat the process for launching FRST from the command prompt, but this time press Fix.

A file called fixlog.txt will be created on your USB afterwards. Please attach it to your next reply and try booting again. If you still cannot boot, please run another SFC Scan and provide a fresh copy of the CBS.log in your next reply.
 

Attachments

The problems persist, although they changed slightly. I guess that's good. :smile9:

SFC
No changes at all: Same error, same log.

DISM (scan and restore)
The vsmraid.inf error disappeared from the log.
The program managed to get further in the scanning and restoring-process (=quitting later) and now with a error message "4448 - The WOF driver encountered a corruption in the compressed file's resource table."


View attachment Logfiles.zip
 
Good job! This is going slow, because I have to provide all the replacements manually, so bear with me, please :)

Please follow the same procedure as before and make sure everything is located on the root of the drive:

1. FRST64.exe
2. fixlist.txt
3. Manifests
4. amd64_dual_c_fsopenfilebackup.inf_31bf3856ad364e35_10.0.17134.1_none_f3c7e5de205531fb
5. amd64_microsoft-windows-font-truetype-segoeui_31bf3856ad364e35_10.0.17134.1_none_b63c90107b671452

Afterwards, attempt to boot again, and if failed, attach the log files just like you did before.
 

Attachments

Now it gets weird...

Boot-situation
Changed drastically... blue Windows logo with spinning circle... then black, then beep from the PC-speaker and bluescreen with smiley and QR-code (error-message: critical process died)

sfc.txt
exits instantly with "Windows Resource Protection could not perform the requested operation"


dism-check
Tells me that the component store cannot be repaired.

dism-scan.txt
exits nearly instantly with "267 - Unable to access the image."

dism-restore.txt
exits nearly instantly with "267 - Unable to access the image."


There is a message in the fixlog that "amd64_microsoft-windows-bcp47languages_31bf3856ad364e35_10.0.17134.1_none_7feada183ffe195f" was missing in your ZIP-file... don't know if that means anything...

View attachment Logfiles.zip

BTW: There is a translation error in the FRST64.exe - the German translation of "fix" is not "entfernen"... "entfernen" is "delete", "fix" would be "reparieren".
It feels strange to click on a delete-button to fix a system. :lol:
 
The Windows recovery OS mounts my usual C-drive to letter F when I enter the command prompt, so it depends on if I run FRST64.exe first (which changes F: to C:) or if I jump directly to the prompt after a reboot without starting FRST64.exe up front.
 
Nope, when FRST starts, it re-maps the drive from F: to C:, so the foldername with the drive letter C: was right.
When I use the fixlist.txt with F:, I get a "path not found" instantly.
 
Just some additional info (all folder names after FRST ran and case-sensitive):
- the path to the quarantine of the Manifests is: c:\FRST\Quarantine\C\Windows\winsxs.
There is a Manifests.xBAD file and a Manifests-folder.

The file c:\Windows\WinSxS\Manifests exists and I can access it via type or notepad.
Besides the file there is a folder ManifestCache in WinSxS.

The size of Manifests and Manifests.xBAD differ.
 
aaand... we are back on track. :-)
Seems like the restore from quarantine tried to copy the folder into a file instead of a folder... dunno, I put the files into the folder and this is the "new" situation:

The system reverted to a black screen with a spinning circle instead of the blue screen.

sfc.txt
exits with "Windows Resource Protection could not perform the requested operation"


dism-analyze.txt
Tells me that the component store can be repaired. (thankfully again)

dism-scan.txt
exits with "605 - The specified buffer contains ill-formed data."

dism-restore.txt
exits with "605 - The specified buffer contains ill-formed data."
 

Attachments

Okay, this takes a little bit longer to explain...

I used your fixlist.txt and the run of FRST64 resulted in an error message (3) for the copy command.
...
That's when I got curious about if there is also a file instead of a folder in the C:\Windows\WinSxS-folder.
And that was the case: All files provided by your ZIPs ended up as files with the foldername but without extension and the size of the last file in the folder.

I deleted them and manually copied over the files from your ZIP.

SFC pointed out a problem with the D2D1.dll under the WinSxS-folder.
I got a working copy of that one from a different Windows 10 installation and tried to make a backup before I would replace it.
That's when the copy and xcopy command presented me with a malformed buffer error.

I deleted that file and replaced it. Ran SFC again.

Same error with C:\Windows\system32\d2d1.dll.

Ran SFC again and got presented a bunch of errors on the C:\Windows\fonts\seguisym.ttf.
Tried to make a backup and got a WOF-driver resource-table error something I saw earlier this day as a dism.exe result.

Replaced that one with the new file in WinSxS.
Ran SFC again.

That logfile is attached to this message.

Started the PC, stranded directly in safe-mode.
Restarted the PC, got safe-mode again.
Turned off PC, turned it on... safe-mode. :-/

Open the Windows options icon from the startmenu... window closes instantly.
Do it again, still closes.

A giantic leap forward, but how do I end the safe-mode? :-)
 

Attachments

Unchecked "boot to safe-mode" in msconfig.exe and I could boot to normal mode. :-)

Yay! (phew)
Is there anything I still need to do cleaning up or bugs open in my last logfile which could cause obvious problems?
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top