T
Teriki
Guest
Windows version: 1909 10.0.18363.836 (System language is Czech, applications' language is English US)
Story:
Got a transient error notification message while gaming, it asked me if I want to fix it, I had clicked yes, closed every running program and waited for some time. Windows was running ok, but some freezes occured just before and then during fixing. When it asked for a reboot to finish its work and during reboot it crashed into blue screen (critical process died) - I let the blue screen run for some time and finish its work - it showed 100% and stayed so for 20+ minutes, so i've turned off my PC (laptop).
Problem:
Since when I can't properly boot up and log in — although windows does boot up and show me a welcome screen (that one with a clock and date, walpaper also does come up) I can't proceed to entering my PIN for my account to enter desktop as it restarts UI (and possibly other tasks/processes) every 2-3 seconds, from a user perspective it seems like explorer.exe keeps restarting due to other services errors. Also to mention: where is nothing behind that screen when I try to swipe it up by mouse or by pressing keys - neither user icon or pin input field, simply welcome screen walpaper and nothing on it.
Won't work:
Restore point has gone, so i can't use it, same with updates rollback option in WinRE.
Tried:
SFC /scannow - system files corrupted, but it states they are repairable.
DISM - /ScanHealth and /CheckHealth say the same thing - corrupted, but repairable. Tried /RestoreHealth with no explicit /Source - not working, "source files could not be found" 0x800f081f. I have another drive with the exact same version windows 10 installation (1909 10.0.18363.836), so I booted it up, connected my corrupted installation drive via usb and used DISM with /Source pointing to the working windows folder, also have tried /Source with Windows Installation USB (created by "MediaCreationTool2004" - not my version, so obviously hasn't worked), WIMs and ESDs of different versions (from 18362.30 to 18363.418, both EN and CZ downloaded from microsoft support db - previously known as tech bench) - repaired some corruptions, but not all of them (still 1514 in total after everything tried)
Here is DISM summary of the last try:
Summary:
2020-06-06 22:36:38, Info CBS Operation: Detect and Repair
2020-06-06 22:36:38, Info CBS Operation result: 0x800f081f
2020-06-06 22:36:38, Info CBS Last Successful Step: Entire operation completes.
2020-06-06 22:36:38, Info CBS Total Detected Corruption: 1514
2020-06-06 22:36:38, Info CBS CBS Manifest Corruption: 13
2020-06-06 22:36:38, Info CBS CBS Metadata Corruption: 0
2020-06-06 22:36:38, Info CBS CSI Manifest Corruption: 711
2020-06-06 22:36:38, Info CBS CSI Metadata Corruption: 0
2020-06-06 22:36:38, Info CBS CSI Payload Corruption: 790
2020-06-06 22:36:38, Info CBS Total Repaired Corruption: 0
2020-06-06 22:36:38, Info CBS CBS Manifest Repaired: 0
2020-06-06 22:36:38, Info CBS CSI Manifest Repaired: 0
2020-06-06 22:36:38, Info CBS CSI Payload Repaired: 0
2020-06-06 22:36:38, Info CBS CSI Store Metadata refreshed: True
Here is link to full dism.log (it constains multiple logs from 4-5 runs of dism with different settings each starting with "<----- Starting Dism.exe session ----->"): dism.log
I've read some of that log and noticed, that some of the files are related to login/startup etc. and some of them are even UI component resources (like "RestartNowPower_80.png" or "AccountLogo.png" or "aero_arrow.cur"). Also, at the beginning DISM logs, that it can't recognize repaired image by some tools, but I guess it's ok. And the thing I found interesting is logs such as:
2020-06-06 22:32:53, Info CBS Exec: Not able to find amd64_microsoft-windows-m..orkhelper.resources_31bf3856ad364e35_10.0.18362.1_en-us_07de6eda09ebb624.manifest from directory local source
2020-06-06 22:32:53, Info CBS Copied file \\?\c:\windows\WinSxS\Manifests\amd64_microsoft-windows-m..orkhelper.resources_31bf3856ad364e35_10.0.18362.1_en-us_07de6eda09ebb624.manifest from directory path: \\?\c:\windows\WinSxS\Manifests\amd64_microsoft-windows-m..orkhelper.resources_31bf3856ad364e35_10.0.18362.1_en-us_07de6eda09ebb624.manifest
So it says it can't find the file, but the next line the same named file is copied.
Question:
So, my question is: is it actually repairable at such state? Or should I just make a factory reset (I know it can save user files), but in that case I'm not even sure if it will work properly (have seen on google, that it can fail too).
Thanks for any help/advice! Hope you'll never encounter such a problem - never let windows to repair itself until you have a valid restore point, never turn off your PC while BSOD.
Continue reading...
Story:
Got a transient error notification message while gaming, it asked me if I want to fix it, I had clicked yes, closed every running program and waited for some time. Windows was running ok, but some freezes occured just before and then during fixing. When it asked for a reboot to finish its work and during reboot it crashed into blue screen (critical process died) - I let the blue screen run for some time and finish its work - it showed 100% and stayed so for 20+ minutes, so i've turned off my PC (laptop).
Problem:
Since when I can't properly boot up and log in — although windows does boot up and show me a welcome screen (that one with a clock and date, walpaper also does come up) I can't proceed to entering my PIN for my account to enter desktop as it restarts UI (and possibly other tasks/processes) every 2-3 seconds, from a user perspective it seems like explorer.exe keeps restarting due to other services errors. Also to mention: where is nothing behind that screen when I try to swipe it up by mouse or by pressing keys - neither user icon or pin input field, simply welcome screen walpaper and nothing on it.
Won't work:
Restore point has gone, so i can't use it, same with updates rollback option in WinRE.
Tried:
SFC /scannow - system files corrupted, but it states they are repairable.
DISM - /ScanHealth and /CheckHealth say the same thing - corrupted, but repairable. Tried /RestoreHealth with no explicit /Source - not working, "source files could not be found" 0x800f081f. I have another drive with the exact same version windows 10 installation (1909 10.0.18363.836), so I booted it up, connected my corrupted installation drive via usb and used DISM with /Source pointing to the working windows folder, also have tried /Source with Windows Installation USB (created by "MediaCreationTool2004" - not my version, so obviously hasn't worked), WIMs and ESDs of different versions (from 18362.30 to 18363.418, both EN and CZ downloaded from microsoft support db - previously known as tech bench) - repaired some corruptions, but not all of them (still 1514 in total after everything tried)
Here is DISM summary of the last try:
Summary:
2020-06-06 22:36:38, Info CBS Operation: Detect and Repair
2020-06-06 22:36:38, Info CBS Operation result: 0x800f081f
2020-06-06 22:36:38, Info CBS Last Successful Step: Entire operation completes.
2020-06-06 22:36:38, Info CBS Total Detected Corruption: 1514
2020-06-06 22:36:38, Info CBS CBS Manifest Corruption: 13
2020-06-06 22:36:38, Info CBS CBS Metadata Corruption: 0
2020-06-06 22:36:38, Info CBS CSI Manifest Corruption: 711
2020-06-06 22:36:38, Info CBS CSI Metadata Corruption: 0
2020-06-06 22:36:38, Info CBS CSI Payload Corruption: 790
2020-06-06 22:36:38, Info CBS Total Repaired Corruption: 0
2020-06-06 22:36:38, Info CBS CBS Manifest Repaired: 0
2020-06-06 22:36:38, Info CBS CSI Manifest Repaired: 0
2020-06-06 22:36:38, Info CBS CSI Payload Repaired: 0
2020-06-06 22:36:38, Info CBS CSI Store Metadata refreshed: True
Here is link to full dism.log (it constains multiple logs from 4-5 runs of dism with different settings each starting with "<----- Starting Dism.exe session ----->"): dism.log
I've read some of that log and noticed, that some of the files are related to login/startup etc. and some of them are even UI component resources (like "RestartNowPower_80.png" or "AccountLogo.png" or "aero_arrow.cur"). Also, at the beginning DISM logs, that it can't recognize repaired image by some tools, but I guess it's ok. And the thing I found interesting is logs such as:
2020-06-06 22:32:53, Info CBS Exec: Not able to find amd64_microsoft-windows-m..orkhelper.resources_31bf3856ad364e35_10.0.18362.1_en-us_07de6eda09ebb624.manifest from directory local source
2020-06-06 22:32:53, Info CBS Copied file \\?\c:\windows\WinSxS\Manifests\amd64_microsoft-windows-m..orkhelper.resources_31bf3856ad364e35_10.0.18362.1_en-us_07de6eda09ebb624.manifest from directory path: \\?\c:\windows\WinSxS\Manifests\amd64_microsoft-windows-m..orkhelper.resources_31bf3856ad364e35_10.0.18362.1_en-us_07de6eda09ebb624.manifest
So it says it can't find the file, but the next line the same named file is copied.
Question:
So, my question is: is it actually repairable at such state? Or should I just make a factory reset (I know it can save user files), but in that case I'm not even sure if it will work properly (have seen on google, that it can fail too).
Thanks for any help/advice! Hope you'll never encounter such a problem - never let windows to repair itself until you have a valid restore point, never turn off your PC while BSOD.
Continue reading...