New
#161
Keep us posted, you are doing a bang-up job! (and that's a good thing!)
Hey thanx a million!😁👍🏻 OK, so a bit of luck fell on me today, havin a root in me spare parts tub, I found a Kingston A400 480Gb SSD - basically the identical same drive to the one with the dodgy windows installation on. So I'm now goin to swap out the drives, clean install on the spare empty drive an create a system hive which is identical to the one that is corrupt, then copy the hive to a USB, put the original drive back in an transplant the fresh system hive into the broken installation, an hopefully cure it or at least get the installation to boot so I repair it an tidy up from the inside... I've been at this since 11am! Oh for the love of it!🙄🤣🤣🤣🤣👍🏻
You must enjoy it or you would never put yourself through the pain
Part of the issue is going to be User Security ID (SID)s. The new registry hive will have different Security IDs for the users.
There are so many things in the registry that get created on a new install of Windows that match only the Windows installation that it was created on, I don't think you will ever repair a corrupted registry by replacing it with a hive from a different installation of Windows.
Hmmmmmmmmmmmmmmmm... I'm beginning to agreeeeeee, but I'm not done yet...
- - - Updated - - -
This is as far as I've got:
Microsoft Windows [Version 10.0.19041.1]
(c) 2019 Microsoft Corporation. All rights reserved.
X:\Windows\System32>sfc /scannow /offbootdir=c:\ /offwindir=c:\windows
Beginning system scan. This process will take some time.
Windows Resource Protection did not find any integrity violations.
X:\Windows\System32>DISM /Image:c:\ /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 10.0.19041.1
Image Version: 10.0.19042.804
Error: 1009
The configuration registry database is corrupt.
The DISM log file can be found at X:\windows\Logs\DISM\dism.log
- - - Updated - - -
@Tekkie Boy,
@philc43 What dya think...
Last edited by b1gt1m; 07 Mar 2021 at 09:52.
@b1gt1m
The drivers hive is also corrupt and therefore cannot be loaded with Restorehealth for repairs.
2021-03-07 14:49:11, Info CBS Failed to load offline \\?\c:\Windows\System32\config\DRIVERS hive from '\\?\c:\Windows\System32\config\DRIVERS' into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/DRIVERS'. [HRESULT = 0x800703f1 - ERROR_BADDB]
2021-03-07 14:49:11, Info CBS Failed to load offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/DRIVERS [HRESULT = 0x800703f1 - ERROR_BADDB]
2021-03-07 14:49:11, Info CBS Failed to load offline DRIVERS hive. [HRESULT = 0x800703f1 - ERROR_BADDB]
2021-03-07 14:49:11, Info CBS Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SOFTWARE
2021-03-07 14:49:11, Info CBS Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SYSTEM
2021-03-07 14:49:11, Info CBS Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SECURITY
2021-03-07 14:49:11, Info CBS Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SAM
2021-03-07 14:49:11, Info CBS Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/COMPONENTS
2021-03-07 14:49:11, Error CBS Failed to load offline store from boot directory: '\\?\c:\' and windows directory: '\\?\c:\Windows\' [HRESULT = 0x800703f1 - ERROR_BADDB]
2021-03-07 14:49:11, Error CBS Failed to initialize store parameters with boot drive: c:\, windows directory c:\Windows, and external directory: [HRESULT = 0x800703f1 - ERROR_BADDB]
2021-03-07 14:49:11, Error CBS Cannot finalize a session that has not been initialized. [HRESULT = 0x800703f1 - ERROR_BADDB]
2021-03-07 14:49:11, Info CBS Session: 3160_206328 finalized. Reboot required: no [HRESULT = 0x800703f1 - ERROR_BADDB]
2021-03-07 14:49:11, Error DISM DISM Package Manager: PID=3160 TID=3176 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800703f1)
2021-03-07 14:49:11, Error DISM DISM Package Manager: PID=3160 TID=3176 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800703f1)
2021-03-07 14:49:11, Error DISM DISM Package Manager: PID=3160 TID=3176 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800703f1)
2021-03-07 14:49:11, Error DISM DISM Package Manager: PID=3160 TID=3176 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800703f1)
2021-03-07 14:49:11, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800703F1
You could take the drivers hive from your parallel installation and replace the defective drivers hive to test.
Backup beforehand the defective drivers hive.
OK, I'll give it a go an keep ya posted... ;-)
- - - Updated - - -
OK so, tried it an got BSOD Critical Failure, but it past the boot stage and was into the kernel... see the files...
Dropbox - MEMORY.DMP - Simplify your life
- - - Updated - - -
I've just downloaded an installed the Windows 10 SDK. How do I use it to open up and view the Memory.dmp file? I mean, you can't obviously view it in Notepad, all you get is a big mess....
WinDbg? Is this part of the sdk? I installed everything... It just occurred to me that I haven't run DISM RestoreHealth with the new driver hive yet!? I'll do it now...
The crash dump file shows the same error when the process Services.exe was running. As you can see the process is terminated. Something must go wrong but I can't work it out. The error code 0xd1b2e080 is not one I can fathom out.
FAILURE_BUCKET_ID: 0xEF_services.exe_BUGCHECK_CRITICAL_PROCESS_d1b2e080_ntdll!NtTerminateProcess
The nice thing is all your Environment Variables are now looking good!
Two tutorials to help you use WinDBG:
https://www.tenforums.com/tutorials/2082-windbg-install-configure.html
https://www.tenforums.com/tutorials/5558-windbg-basics-debugging-crash-dumps-windows-10-a.html