question

FXE-9887 avatar image
0 Votes"
FXE-9887 asked FXE-9887 answered

CRITICAL_SERVICE_FAILED at Windows 2016 boot

Hi all,

Since last saturday, we face an Windows Server 2016 boot failure with error "CRITICAL_SERVICE_FAILED".
This happened following our Windows Update cycle, so I guessed it was due to last installed updates.

Then, I restored system disk (via Veeam B&R) 1 day before update, and same issue !
So it seems to not be related to Windows Update.

The only way I have found to make Windows boot "normally" is to chose "boot without drivers signature verification".
After this "successful" boot, I applied latest updates from our WSUS, but the next reboot attempt failed.

sfc /scannow command shows there are errors it cannot repair.
I have launched DISM /Online /Cleanup-Image /RestoreHealth command which has finished correctly, then relaunched sfc /scannow and and no change...

Every time I reboot this VM (under VMware 6.7), boot fails and I have to select "boot without drivers signature verification".

We have several VM based on the same image without any issue.

Any idea please ?
Thank you.

Regards,

windows-server-2016
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@FXE-9887
Hi,

Just checking in to see if the information provided was helpful.

If the reply helped you, please remember to accept as answer.
If no, please reply and tell us the current situation in order to provide further help.

0 Votes 0 ·

@FXE-9887
Hi,

We have not get information from you for several days.

If the reply is useful for you, please accept as answer. It will be helpful to other members who have same questions.
If you have any other confuse, please reply to us directly.

0 Votes 0 ·
Docs-4663 avatar image
0 Votes"
Docs-4663 answered Docs-4663 published

There were no misbehaving drivers seen in the memory dump on Mon Jun 14 16:38:28.717 2021 (UTC - 5:00).

Options:
a) monitor for unexpected shutdowns and restarts / BSOD > debug any new dump files
b) perform regback
c) if some downtime is possible then stress test non-Microsoft drivers with Windows driver verifier
d) clean install: https://www.windowsservercatalog.com/


.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post: Vote = a helpful post
.
.
.
.
.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

FXE-9887 avatar image
0 Votes"
FXE-9887 answered FXE-9887 edited

Hi all and thank you for your answers,

As expected, issue has been reproduced last saturday night following our scheduled reboot process.

Last Wednesday, I've opened 1 case vs Microsoft Support and I'm always waiting for a "professional" answer from them as I received the following :

"Thank you for reaching out to Microsoft Windows Commercial Support. I'm the Queue Manager for Windows Commercial EMEA. I would like to acknowledge that we have received your case and inform you that we haven’t been able yet to define an owner for the case. The reason for this is the high volume of cases coming in at the moment across Europe. Attending to the case severity and the current volumes, we will most probably have an owner for this case in 2-3 business days. Whilst I certainly appreciate this is not the expected service level you're accustomed too, I would like to assure you, we are working diligently to ensure an owner is assigned as soon as possible.
We do appreciate your understanding and cooperation.
"

No reply until now... I guess the billions are focused on another things than prepaid business services...

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Docs-4663 avatar image
0 Votes"
Docs-4663 answered Docs-4663 edited

Regback may be a viable fix.


.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post: Vote = a helpful post
.
.
.
.
.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

FXE-9887 avatar image
0 Votes"
FXE-9887 answered

As I understand, regback is a tool to backup registry, but I don't have this tool enabled on this server.
So I'm not sure to understand what you want I do in this situation.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Docs-4663 avatar image
0 Votes"
Docs-4663 answered

See Method 5: Restore System Hive
https://docs.microsoft.com/en-us/windows/client-management/advanced-troubleshooting-boot-problems

There are different methods for copying the automatic regback files.

Automatic regback was once the default option on Windows.

Each computer may be different as to whether the files are available / sizable.

https://pureinfotech.com/restore-registry-backup-windows-10/
https://www.youtube.com/watch?v=AFKHWUS9g8g


Let's see if this is a possible fix.

1) boot to any Windows iso
2) it may take 5 minutes displaying the windows icon
3) Use the default settings for language, time, currency, and keyboard
4) click next
5) In the left lower corner click Repair your computer
6) click troubleshooting
7) click command prompt
You should see a pop up with title bar: Administrator: X:\windows\system32\cmd.exe

This is the registry backup method:

For each step you must see sizable file sizes for this to work.

If you see zeros the method will fail.

The command: dir
will be used each step to make sure you are in the proper location and check the size of the files
8) type: C:
9) dir
10) type: D:
11) dir
Choose the C: or the D: drive to proceed. It should be the windows drive and not the USB drive.

12) type: bcdedit | find "osdevice"
This should display the location of the partition and in most cases is the location of the affected drive.

For this post I will use C: however you should pick the drive letter that you found that has the windows files on your computer.
The proper drive will display: perflogs, program files, program files (x86), users, windows, etc.

13) type or copy and paste: cd \windows\system32\config
It should display: C:\windows\system32\config>

14) type: dir
It should display: bbi, bcd-template, components, default, drivers, elam, sam, security, software, system, vsmidk, journal, regback, systemprofile txr, etc.
All of the file sizes should be sizable. If it displays zeros then abort.

Make a new directory and name it backup or something similar.
15) type: MD backup
Copy all of the files into this new directory.

16) type or copy and paste: copy . backup
It should now display: bbi, bcd-template, components, default, drivers, elam, sam, security, software, system, vsmidk indicating the files were copied.

Change the directory to regback
17) type: cd regback
It should now display: c:\windows\system32\config\regback>

18)type: dir
It should display: default, sam, security, software, system etc
All of these files must be sizable. If it displays zeros then abort.

19) type or copy and paste: copy . ..
It should now display:
DEFAULT
Overwrite ..\default? (yes/no/all):

20) type: a
It should now display: sam, security, software, system and that the files were copied.

21) type: exit
22) click turn off your PC
Remove the USB flash drive if you had changed your boot order. Otherwise you can leave it and power on your computer.




.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post: Vote = a helpful post
.
.
.
.
.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.