[SOLVED] got a blue screen :( and I can't run SFC. Err. 0x74:Bad_system_config_info; DEFAULT hive corrupt. FIX: I replaced it with the one in W10-20H2-eng ISO.

Did you try to change the esp gpt attributes?

Another thing to try: if you didn't already do it, download the windows 10 media creation tool and create the windows 10 installation media (USB or CD).

Then:
Rich (BB code):
dism /image:YourWindowsDriveLetter:\windows /cleanup-image /restorehealth /source:esd:YourESDDriveLetter:\sources\install.esd:x

Index 1 should be for windows 10 home
Index 5 should be for windows 10 pro
can I run this command from the Windows RE? I have a usb with windows 10 installation too. I will try doing the dism command first then change
 
I think I'll leave the gpt attribute cause it should be fine, is fresh.
I ran the dism command and got errors, the error said "make sure that the image path and the windows directory for the image exist and I have read permission.
I checked and yes I have read and write permissions on c:\windows
I used the esd from usb drive, drive letter for the esd was g. Was it suppose to copy files from the pen drive to my c drive? Also why :x not :g or :c?
I'm attaching the dism log, I ran it 2 or 3 times.
 

Attachments

Last edited:
You used the x for the index, but you should change it according to your OS index (re-check my previous reply in the code).

If you are using windows 10 home, index should be 1; hence:
Rich (BB code):
dism /image:c:\windows /cleanup-image /restorehealth /source:esd:g:\sources\install.esd:1

If you are using another listed version, you must use its index.
Another example; if you are using Windows 10 Education N, index is 4:
Rich (BB code):
dism /image:c:\windows /cleanup-image /restorehealth /source:esd:g:\sources\install.esd:4
 
You used the x for the index, but you should change it according to your OS index (re-check my previous reply in the code).

If you are using windows 10 home, index should be 1; hence:
Rich (BB code):
dism /image:c:\windows /cleanup-image /restorehealth /source:esd:g:\sources\install.esd:1

If you are using another listed version, you must use its index.
Another example; if you are using Windows 10 Education N, index is 4:
Rich (BB code):
dism /image:c:\windows /cleanup-image /restorehealth /source:esd:g:\sources\install.esd:4
ok but still got same error, I used code 5. and I type exactly you wrote but used 5.
here's the latest log.
 

Attachments

If you have free space on c:, create the scratchdir directory on it:
Code:
md c:\scratchdir

Then try this command:
Code:
dism /image:c:\windows /scratchdir:c:\scratchdir /cleanup-image /restorehealth /source:esd:g:\sources\install.esd:5 /limitaccess
 
Last edited:
I tried to perform some commands in the recovery environment and they worked; my drive got the D letter:
Code:
sfc /scannow /offbootdir=d:\ /offwindir:d:\windows
dism /image:d:\ /cleanup-image /restorehealth

(I used scanhealth instead of restorehealth, but it should work)

Let me know if this works, otherwise I could try the procedure from the windows 10 iso.
 
Last edited:
I tried to perform some commands in the recovery environment and they worked; my drive got the D letter:
Code:
sfc /scannow /offbootdir=d:\ /offwindir:d:\windows
dism /image:d:\ /cleanup-image /restorehealth

(I used scanhealth instead of restorehealth, but it should work)

Let me know if this work, otherwise I could try the procedure from the windows 10 iso.
it didn't work same error 2.
I tried it in different ways, this way-> g:\sources\install.esd:5 and then tried going into g:\sources and just typed install.esd:5
let's try the image mode.
 
Please display the result from:
dism /image:c:\windows /scratchdir:c:\scratchdir /cleanup-image /restorehealth /source:esd:g:\sources\install.esd:5 /limitaccess

Did all of the Dism commands fail in Windows RE?
 
Please display the result from:
dism /image:c:\windows /scratchdir:c:\scratchdir /cleanup-image /restorehealth /source:esd:g:\sources\install.esd:5 /limitaccess

Did all of the Dism commands fail in Windows RE?
it said Error: 2
unable to access the image.
make sure that the image path and windows directory for the image exist, and you have read permissions on the folder.

I'll try those 2 commands in windows RE in a bit. But I believe I tried the first dism command in RE and it gave me the same error.
 
Please display results for these commands:

bcdedit | find "osdevice"
DISM /image:X:\ /cleanup-image /revertpendingactions

(replace X with the drive letter for the partition)

(reboot)

bootrec /fixboot
bootrec /scanos
bootsect /nt60 sys

(reboot)
 
Please display results for these commands:

bcdedit | find "osdevice"
DISM /image:X:\ /cleanup-image /revertpendingactions

(replace X with the drive letter for the partition)

(reboot)

bootrec /fixboot
bootrec /scanos
bootsect /nt60 sys

(reboot)
Why should I execute bootrec? isn't it for MBR disks? I could if you want me to run windows this way.
------------------------------
result from first command:
G:\>bcdedit | find "osdevice"
osdevice partition=C:

result from second command:
G:\>dism /image:c:\ /cleanup-image /revertpendingactions

Deployment Image Servicing and Management tool
Version: 10.0.19041.1

Image Version: 10.0.19042.662

The scratch directory size might be insufficient to perform this operation. This can cause unexpected behavior.
Use the /ScratchDir option to point to a folder with sufficient scratch space. The recommended size is at least 1024 MB.

Reverting pending actions from the image...

Error: 1009

An error occurred reverting the pending actions from the image.
For more information, review the log file.

The DISM log file can be found at X:\windows\Logs\DISM\dism.log

G:\>dism /image:c:\ /scratchdir:c:\scratch /cleanup-image /revertpendingactions

Deployment Image Servicing and Management tool
Version: 10.0.19041.1

Image Version: 10.0.19042.662

Reverting pending actions from the image...

Error: 1009

An error occurred reverting the pending actions from the image.
For more information, review the log file.

The DISM log file can be found at X:\windows\Logs\DISM\dism.log

G:\>

-------------------------
I have scratchdir as c:\scratch that's how I created it. And at first i didn't specify the scratchdir directory, second try i did.

Maybe you will see something in the log from dism atached.
 

Attachments

Please open a thread in the Windows update forum and post a link into this thread.

Code:
HRESULT = 0x800703f1 - ERROR_BADDB
 
Error code: (HRESULT) 0x800703f1 = The configuration registry database is corrupt


Code:
2021-01-11 17:27:17, Info                  CBS    Loading offline registry hive: SOFTWARE, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SOFTWARE' from path '\\?\c:\Windows\System32\config\SOFTWARE'.
2021-01-11 17:27:18, Info                  CBS    Loading offline registry hive: SYSTEM, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SYSTEM' from path '\\?\c:\Windows\System32\config\SYSTEM'.
2021-01-11 17:27:18, Info                  CBS    Loading offline registry hive: SECURITY, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SECURITY' from path '\\?\c:\Windows\System32\config\SECURITY'.
2021-01-11 17:27:18, Info                  CBS    Loading offline registry hive: SAM, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SAM' from path '\\?\c:\Windows\System32\config\SAM'.
2021-01-11 17:27:18, Info                  CBS    Loading offline registry hive: COMPONENTS, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/COMPONENTS' from path '\\?\c:\Windows\System32\config\COMPONENTS'.
2021-01-11 17:27:18, Info                  CBS    Loading offline registry hive: DRIVERS, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/DRIVERS' from path '\\?\c:\Windows\System32\config\DRIVERS'.
2021-01-11 17:27:18, Info                  CBS    Loading offline registry hive: DEFAULT, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/DEFAULT' from path '\\?\c:\Windows\System32\config\DEFAULT'.
2021-01-11 17:27:18, Info                  CBS    Failed to load offline \\?\c:\Windows\System32\config\DEFAULT hive from '\\?\c:\Windows\System32\config\DEFAULT' into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/DEFAULT'. [HRESULT = 0x800703f1 - ERROR_BADDB]
2021-01-11 17:27:18, Info                  CBS    Failed to load offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/DEFAULT [HRESULT = 0x800703f1 - ERROR_BADDB]
2021-01-11 17:27:18, Info                  CBS    Failed to load offline DEFAULT hive. [HRESULT = 0x800703f1 - ERROR_BADDB]
2021-01-11 17:27:18, Info                  CBS    Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SOFTWARE
2021-01-11 17:27:18, Info                  CBS    Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SYSTEM
2021-01-11 17:27:18, Info                  CBS    Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SECURITY
2021-01-11 17:27:18, Info                  CBS    Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SAM
2021-01-11 17:27:18, Info                  CBS    Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/COMPONENTS
2021-01-11 17:27:18, Info                  CBS    Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/DRIVERS
2021-01-11 17:27:18, Error                 CBS    Failed to load offline store from boot directory: '\\?\c:\' and windows directory: '\\?\c:\Windows\' [HRESULT = 0x800703f1 - ERROR_BADDB]
2021-01-11 17:27:18, Error                 CBS    Failed to initialize store parameters with boot drive: c:\, windows directory c:\Windows, and external directory:  [HRESULT = 0x800703f1 - ERROR_BADDB]
2021-01-11 17:27:18, Error                 CBS    Cannot finalize a session that has not been initialized. [HRESULT = 0x800703f1 - ERROR_BADDB]
2021-01-11 17:27:18, Info                  CBS    Session: 976_587000 finalized. Reboot required: no [HRESULT = 0x800703f1 - ERROR_BADDB]
2021-01-11 17:27:18, Error                 DISM   DISM Package Manager: PID=976 TID=1264 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800703f1)
2021-01-11 17:27:18, Error                 DISM   DISM Package Manager: PID=976 TID=1264 An error occured clearing the pending actions from the image. - CDISMPackageManager::RevertPendingActions(hr:0x800703f1)
2021-01-11 17:27:18, Error                 DISM   DISM Package Manager: PID=976 TID=1264 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800703f1)
 
everytime I run sfc /scannow from the recovery enviroment not while on Windows 10 cause I can't get to windows desktop, it gets to 100% scanning and then says resource protection can't perform the requested operation. I tried tutorials to fix this and still get the same error. I think if I run succesfuly SFC /scannow I'll get my windows 10 back again. It will started when I switched the power switch to off instead then shutting down as usual. I don't think there is any other errors other than corrupted system files can someone check this with me?

I tried startup auto repair but it doesn't fix it as shown on the photograph.
View attachment 64795View attachment 64796
View attachment 64797That's my current partition setup on Disk 0 and the only partition with windows 10 is partition 3.
Yesterday, I had this issue on my lenovo x260 laptop. I remove the battery and put after sometimes into my laptop but the windows autorepair automatically perform and system restore the issue will resolved! but the issue comes after the windows upgrade because some files won't support the system files.
 
For the iso: pro should be 6.


Type:

diskpart
lis dis
lis vol
exit
bcdedit | find "osdevice"

See if this command can run in Windows RE


Change C: and or G: as needed:

dism /image:c:\windows /scratchdir:c:\scratchdir /cleanup-image /restorehealth /source:esd:g:\sources\install.esd:6 /limitaccess


Post new CBS and DISM share links.
 
Last edited:
failed again.
C:\scratch>diskpart

Microsoft DiskPart version 10.0.19041.1

Copyright (C) Microsoft Corporation.
On computer: MININT-TN71Q4C

DISKPART> list disk

Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 232 GB 1024 KB *
Disk 1 Online 111 GB 0 B
Disk 2 Online 465 GB 0 B
Disk 3 Online 113 GB 0 B
Disk 4 Online 953 GB 0 B
Disk 5 No Media 0 B 0 B
Disk 6 Online 28 GB 0 B

DISKPART> list vol

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 C NTFS Partition 232 GB Healthy
Volume 1 I NTFS Partition 499 MB Healthy
Volume 2 FAT32 Partition 100 MB Healthy Hidden
Volume 3 D 500GB NTFS Partition 465 GB Healthy
Volume 4 E 120GB Apple exFAT Partition 112 GB Healthy
Volume 5 F exFAT Partition 953 GB Healthy
Volume 6 H Removable 0 B No Media
Volume 7 G ESD-USB FAT32 Removable 28 GB Healthy

DISKPART> exit

Leaving DiskPart...

C:\scratch>bcdedit | find "osdevice"
osdevice partition=C:

C:\scratch>dism /image:c:\windows /scratchdir:c:\scratch /cleanup-image /restorehealth /source:esd:g:\sources\install.esd:6 /limitaccess

Deployment Image Servicing and Management tool
Version: 10.0.19041.1


Error: 2

Unable to access the image.
Make sure that the image path and the Windows directory for the image exist and you have Read permissions on the folder.

The DISM log file can be found at X:\windows\Logs\DISM\dism.log

C:\scratch>


I HAVE NO IDEA WHY STILL NOT APPLYING CHANGES. MAYBE TROBLE SHOOT THE HIVE I PUBLISIZED?
 

Attachments

Will the embootkit-1.6k-demo fix my hive or registry issue? I was thinking it might but now I'm not sure, and it costs money.
 
The CBS log was dated 12/04/20

The DISM log displayed:

Code:
2021-01-13 02:10:43, Info                  DISM   DISM.EXE: Executing command line: dism  /image:c:\windows /scratchdir:c:\scratch /cleanup-image /restorehealth /source:esd:g:\sources\install.esd:6 /limitaccess
2021-01-13 02:10:43, Info                  DISM   DISM Provider Store: PID=1744 TID=1748 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2021-01-13 02:10:43, Info                  DISM   DISM Provider Store: PID=1744 TID=1748 Connecting to the provider located at X:\windows\system32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2021-01-13 02:10:43, Warning               DISM   DISM Provider Store: PID=1744 TID=1748 Failed to load the provider: X:\windows\system32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2021-01-13 02:10:43, Info                  DISM   DISM Provider Store: PID=1744 TID=1748 Connecting to the provider located at X:\windows\system32\Dism\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2021-01-13 02:10:43, Info                  DISM   DISM Provider Store: PID=1744 TID=1748 Connecting to the provider located at X:\windows\system32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2021-01-13 02:10:43, Info                  DISM   DISM Provider Store: PID=1744 TID=1748 Connecting to the provider located at X:\windows\system32\Dism\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2021-01-13 02:10:43, Info                  DISM   DISM Provider Store: PID=1744 TID=1748 Connecting to the provider located at X:\windows\system32\Dism\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2021-01-13 02:10:43, Warning               DISM   DISM Provider Store: PID=1744 TID=1748 Failed to load the provider: X:\windows\system32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

0x8007007e = The specified module could not be found.



Embootkit-1.6k-demo I'v not seen anyone use.

A reset save files equivalent is another possible fix (reinstall drivers and applications).

The Windows update forum is the next troubleshooting option.
 

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

Back
Top