hey guys so im having non bootable system all of a sudden. using win10 pro 22H2 on mbr. when trying to boot i keep getting "preparing automatic repair"\diagnosing you pc. then windows is trying to repair but unsuccessfully "your pc did not start correctly".. Attempting repairs etc etc after this im trying myself the Startup Repair but the same it dosent work. also automatic repair couldnt fix the boot getting LOG file: I:\WINDOWS\System32\Logfiles\Srt\SrtTrail.txt when opening the log file i mostly see that winload.exe is corrupt with 0x490 code + boot manager is corrupt. tried bootrec \rebuildbcd didnt find nothing (except one time..) bootrec\scan os find nothing fixmbr completed ok fixboot is access denied.. what is going on? i tried sfc did not help,tried replacing the winload with a fresh copy didnt help either.
hey DriftiX try from recovery SFC [/SCANNOW] [/VERIFYONLY] [/SCANFILE=<file>] [/VERIFYFILE=<file>] [/OFFWINDIR=<offline windows directory> /OFFBOOTDIR=<offline boot directory> [/OFFLOGFILE=<log file path>]] with the offline parameters to fix those damage files like winload.exe
check with diskpart.exe and "list volume" the drives letters mb like this SFC /SCANNOW /OFFWINDIR=c:\windows /OFFBOOTDIR=d:\EFI
when i tried scanfile with offbootdir + offwindir, im getting "found corrupt file but was unable to fix some of them"
winsxs folder has been removed ig is it lite version ? try copy the files that got damaged from iso or use dism /online /cleanup-image /RestoreHealth /source:wim:\sources\install.wim:3 for example if this iso is original u can try install 7zip on the recovery env and look for the install.wim and the file u need
il try this. meanwhile here is the log file from the command you told me before: Code: 00000001 Shim considered [l:126]'\??\j:\windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.4585_none_7e06e2187c9234e2\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND 00000002 Shim considered [l:123]'\??\j:\windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.4585_none_7e06e2187c9234e2\wcp.dll' : got STATUS_SUCCESS 00000001@2024/7/18:08:28:52.329 WcpInitialize: wcp.dll version 10.0.19041.4585 (WinBuild.160101.0800) 00000002 CSI Store 1602478332960 initialized 00000003 [SR] Verifying 1 components 00000004 [SR] Beginning Verify and Repair transaction 00000005 Hashes for file member [l:11]'winload.exe' do not match. Expected: {l:32 ml:33 b:e74e12fdcbc9e5f4246beeb88315d8ea92e0afbf352659a9d9a672f7167ada16}. Actual: {l:32 b:239c1571c091628a7315d4adb1e41f4d13bf5b2753cca9871e377e48d9e4c412}. 00000006 [SR] Cannot repair member file [l:11]'winload.exe' of Microsoft-Windows-BootEnvironment-OS-Loader, version 10.0.19041.4648, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch 00000007 [SR] Unable to repair \??\C:\WINDOWS\WinSxS\Manifests\\[l:110 ml:149]'amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e35_10.0.19041.4648_none_cfbf259621fa9e3e.manifest' 00000008 Hashes for file member [l:11]'winload.exe' do not match. Expected: {l:32 ml:33 b:e74e12fdcbc9e5f4246beeb88315d8ea92e0afbf352659a9d9a672f7167ada16}. Actual: {l:32 b:239c1571c091628a7315d4adb1e41f4d13bf5b2753cca9871e377e48d9e4c412}. 00000009 [SR] Unable to repair \??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e35_10.0.19041.4648_none_cfbf259621fa9e3e\\[l:11]'winload.exe' 0000000a Hashes for file member [l:11]'winload.exe' do not match. Expected: {l:32 ml:33 b:e74e12fdcbc9e5f4246beeb88315d8ea92e0afbf352659a9d9a672f7167ada16}. Actual: {l:32 b:239c1571c091628a7315d4adb1e41f4d13bf5b2753cca9871e377e48d9e4c412}. 0000000b [SR] Cannot repair member file [l:11]'winload.exe' of Microsoft-Windows-BootEnvironment-OS-Loader, version 10.0.19041.4648, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch 0000000c [SR] This component was referenced by [l:158]'Microsoft-Windows-Client-Desktop-Required-Package0515~31bf3856ad364e35~amd64~~10.0.19041.4648.B7883D970FF946B679750D5ED282C8988D2E35E381D809B9FAF19CBA06C0BADD' 0000000d [SR] Verify complete 0000000e [SR] Repairing 1 components 0000000f [SR] Beginning Verify and Repair transaction 00000010 Hashes for file member [l:11]'winload.exe' do not match. Expected: {l:32 ml:33 b:e74e12fdcbc9e5f4246beeb88315d8ea92e0afbf352659a9d9a672f7167ada16}. Actual: {l:32 b:239c1571c091628a7315d4adb1e41f4d13bf5b2753cca9871e377e48d9e4c412}. 00000011 [SR] Cannot repair member file [l:11]'winload.exe' of Microsoft-Windows-BootEnvironment-OS-Loader, version 10.0.19041.4648, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch 00000012 [SR] Unable to repair \??\C:\WINDOWS\WinSxS\Manifests\\[l:110 ml:149]'amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e35_10.0.19041.4648_none_cfbf259621fa9e3e.manifest' 00000013 Hashes for file member [l:11]'winload.exe' do not match. Expected: {l:32 ml:33 b:e74e12fdcbc9e5f4246beeb88315d8ea92e0afbf352659a9d9a672f7167ada16}. Actual: {l:32 b:239c1571c091628a7315d4adb1e41f4d13bf5b2753cca9871e377e48d9e4c412}. 00000014 [SR] Unable to repair \??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e35_10.0.19041.4648_none_cfbf259621fa9e3e\\[l:11]'winload.exe' 00000015 Hashes for file member [l:11]'winload.exe' do not match. Expected: {l:32 ml:33 b:e74e12fdcbc9e5f4246beeb88315d8ea92e0afbf352659a9d9a672f7167ada16}. Actual: {l:32 b:239c1571c091628a7315d4adb1e41f4d13bf5b2753cca9871e377e48d9e4c412}. 00000016 [SR] Cannot repair member file [l:11]'winload.exe' of Microsoft-Windows-BootEnvironment-OS-Loader, version 10.0.19041.4648, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch 00000017 [SR] This component was referenced by [l:158]'Microsoft-Windows-Client-Desktop-Required-Package0515~31bf3856ad364e35~amd64~~10.0.19041.4648.B7883D970FF946B679750D5ED282C8988D2E35E381D809B9FAF19CBA06C0BADD' 00000018 [SR] Repair complete 00000019 Direct SIL provider: Number of files opened: 61. 0000001a Direct SIL provider: Number of files opened: 5. 00000003 Servicing stack shim unable to mark handle 258 ('\Device\Ramdisk{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}\Windows\temp\SSS_9cec2a85ecd8da010100000014051805\msdelta.dll') for delete-on-close, error STATUS_CANNOT_DELETE 00000004 Servicing stack shim unable to mark handle 18c ('\Device\Ramdisk{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}\Windows\temp\SSS_9cec2a85ecd8da010100000014051805') for delete-on-close, error STATUS_DIRECTORY_NOT_EMPTY
not is regular version... maybe something to do with dism++ with clean sxs option has to do with it? havent had any probs before... wait how to do this dism command online? i cant boot. you specified online
then its should be d:\boot\ "dism++ with clean sxs" removing winsxs files can make recovering using sfc.exe fail yea u cant do the online cmd so do it offline with /image but u will need to deploy the install.wim to folder and then use it as source like /source:\windows.old\windows
it seems the tools dont like my install.wim\winload.copies - its all fresh good ones. somehow it dosent want them, it doesnt make any sense just for a note - this system dual booting - so the main system + 2 vhdx. those 2 are working\booting. only the main is not - maybe its says something to you
oh.. how could this be? iv seen people use it.. on other forum. so what can you suggest guys now? i perfer not to format this system
Code: DISM /image:I:\ /cleanup-image /restorehealth /source:wim:J:\wim_file\install.wim:6 /ScratchDir="J:\work" try this then from my tests it doesnt work
ya it doesn't work, but also source as mounted wim dont work. iv tried manually replacing the corrupted winload.exe file from various isos (22h2\21h2\1909). still no go.. how to know witch version i need exactly for my system