We help IT Professionals succeed at work.

Bad_system_config_info on server 2016

Server 2016 boot loop
I get a bad_system-config_info BSOD, and I cannot seem to bypass this.

The error occured after installing .net framework 4.7.2.

The f8 menu does not help, all options result in the same bsod.

Does anyone have any suggestion what to do to get the system back and running?
Watch Question

Distinguished Expert 2019

All commands should be run from an elevated command prompt.
Run dism /online /cleanup-image /scanhealth.
Run dism /online /cleanup-image /checkhealth.
Run dism /online /cleanup-image /restorehealth.
Mount the Windows Server 2016 ISO as a drive (E: in this case)
Run dism /online /cleanup-image /restorehealth.

after a couple of  reboots, it should start the automatic repair, from which you can access  the command prompt
or use one of these methods :
Rene ChristensenVirksomhedsejer


hmm. I get a cleanup-image is unknown in WinRE
Error 87
Rene ChristensenVirksomhedsejer


I tried
dism /image:D:\ /cleanup-image /scanhealth

But I get an error
An error occured while attempting to access the image
Distinguished Expert 2019

What type is the storage subsystem (hard disk drive(s)) and have you verified its health?
Rene ChristensenVirksomhedsejer


I do have a server 2016 installation USB.
Thats the one I use to enter WinRE
I stil get that error
I have read about something with a /source parameter, but i cannot get it right.
Would you happen to know which command to write?
Rene ChristensenVirksomhedsejer


Its on a raid 10.
I am running a chkdsk right now.
I have run a memory test and a hard drive test.
They both returned no issues.
Are you comfortable with MSDos?

And here is an article on fixing your BSOD (which also applies to servers):

But; before you do any of the restore registry commands, you need to verify that the REGBACK folder contains files that are NOT 0MB (zero)!

Your error 87 running DISM, BTW, indicates a syntax error in  your command line.
Rene ChristensenVirksomhedsejer


Yes I do have a bit of MSdos experience.

I just closed this tread, as I initially had a bcd error, which was fixed.


The error occured after the .net installation.

Your comment could indicate that even though we managed to make windows at least try to boot, the problem might still consist in the former problem.

I'll try your solution, and let you know.
Rene ChristensenVirksomhedsejer


The regback had no zero sized files.

Ran through these:
CD D:\Windows\System32\config
ren D:\Windows\System32\config\DEFAULT DEFAULT.old
ren D:\Windows\System32\config\SAM SAM.old
ren D:\Windows\System32\config\SECURITY SECURITY.old
ren D:\Windows\System32\config\SOFTWARE SOFTWARE.old
ren D:\Windows\System32\config\SYSTEM SYSTEM.old
And after those are done, type in these, one by one, in the given sequence,

copy D:\Windows\System32\config\RegBack\DEFAULT D:\Windows\System32\config\
copy D:\Windows\System32\config\RegBack\SAM D:\Windows\System32\config\
copy D:\Windows\System32\config\RegBack\SECURITY D:\Windows\System32\config\
copy D:\Windows\System32\config\RegBack\SYSTEM D:\Windows\System32\config\
copy D:\Windows\System32\config\RegBack\SOFTWARE D:\Windows\System32\config\

After reboot the circle is spinning for about 10 minutes while the HDD LED flashes and indicates activity.

It all ends in another BSOD:

After automatic restart the system is checking my hard drive for consistency followed by another automatic reboot.
Once again it wants to check the disk, this time i cancel it, and I see just a black screen with no spinning circle.
The HDD LED flashes and indicates activity.
Its like that in at least 30 minutes until I finally ends up in another BSod: Critical_Process_Died
Rene ChristensenVirksomhedsejer


After the reboot i get an error
Windows failed to start:

The operating system couldn't be loaded because a required file is missing or contains errors.
Rene ChristensenVirksomhedsejer


Entered WinRE
Ran startrep from x:\source\recovery.
Not able to repair.

And now, all of a sudden, diskpart shows that my OS partition filformat is raw?
The fact that the OS partition now reports as raw strongly indicates a hardware problem; either with the hard disk subsystem or with ram memory; but, the drives will be very difficult to retrieve much of anything from because RAID 10 is a striped mirror.  What is the controller for the RAID and do you have any ability to test the drives individually?
Distinguished Expert 2019

you could start by testing ram and disk; for ram i use memtest86+ : https://www.memtest.org/
for disk test use the manufacturers tools
I tested both ram and hard drives, but found nothing.
Only som minor errors on chkdsk.

I ended up reinstalling the server.
So unfortunately I never found a reason why things went so wrong as it did.

The boot sector could have been trashed for a longer time ago, just waiting for the first restart to crash the server.
Otherwise the .net framework 4.7.2 installation did something terrible (not that it would make much sense)