Share via

CRITICAL_SERVICE_FAILED at Windows 2016 boot

FXE 516 Reputation points
2021-06-15T13:09:49.533+00:00

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 for business | Windows Server | User experience | Other
Accepted answer
  1. FXE 516 Reputation points
    2021-06-28T20:23:36.193+00:00

    Hi all,

    Finally, thanks to DELL Software Support Team, our server is now fully operational.

    The issue was missing files in folder C:\Windows\System32\CatRoot{F750E6C3-38EE-11D1-85E5-00C04FC295EE} serving drivers signatures.

    The solution was to copy all the files in this folder from another Windows Server 2016 to the folder on affected server without overwrite existing files, and then reboot affected server.

    Thank you all again for your help.

    PS : I'm always waiting for a enterprise-class answer from Microsoft Support.......... Is my paid Software Assurance is really useful ?

    2 people found this answer helpful.
    0 comments

14 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jenny Feng 14,246 Reputation points
    2021-06-16T02:15:17+00:00

    @FXE
    Hi,
    Probably the signature of the driver was bad or unknown and Windows was forcing it to be valid, so it was crashing whole system.
    Then I suggest you update all the drivers to see if it solves the problem.
    For your reference:
    https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/troubleshoot-common-blue-screen-error#collect-memory-dump-file

    Hope above information can help you.

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread

    0 comments
  2. Docs 15,846 Reputation points
    2021-06-16T03:05:04.597+00:00

    The computer has scannow and boot problems.

    Please post results:

    Open administrative command prompt and copy and paste:
    sfc /scannow
    dism /online /cleanup-image /scanhealth
    dism /online /cleanup-image /restorehealth
    sfc /scannow

    When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    CBS and CBS persist may take time to troubleshoot.

    Consider performing a Regback which should fix both scannow and boot problems.

    After a successful Regback:
    a) make a new restore point
    b) make a free backup image > save the image to another disk drive or the cloud
    c) update Windows
    d) if there are any problems perform a system restore or restore the image
    e) logs can be collected for scanning and troubleshooting

    0 comments
  3. FXE 516 Reputation points
    2021-06-16T11:44:34.267+00:00

    Below the results, in french sorry : 

    Microsoft Windows [version 10.0.14393]
(c) 2016 Microsoft Corporation. Tous droits réservés.

C:\Users\Administrateur>sfc /scannow

Début de l’analyse du système. Cette opération peut nécessiter un certain temps.

Démarrage de la phase de vérification de l’analyse du système.
La vérification 100% est terminée.
La protection des ressources Windows a trouvé des fichiers endommagés, mais
n’a pas réussi à tous les réparer. Des détails sont inclus dans le journal
CBS.Log windir\Logs\CBS\CBS.log. Par exemple C:\Windows\Logs\CBS\CBS.log. Notez que la journalisation n’est pas actuellement
prise en charge dans les scénarios de service hors connexion.

C:\Users\Administrateur>dism /online /cleanup-image /scanhealth

Outil Gestion et maintenance des images de déploiement
Version : 10.0.14393.4169

Version de l’image : 10.0.14393.4169

[==========================100.0%==========================] Aucun endommagement du magasin de composants n’a été détecté.
L’opération a réussi.

C:\Users\Administrateur>dism /online /cleanup-image /restorehealth

Outil Gestion et maintenance des images de déploiement
Version : 10.0.14393.4169

Version de l’image : 10.0.14393.4169

[==========================100.0%==========================] La restauration a été effectuée.
L’opération a réussi.

C:\Users\Administrateur>sfc /scannow

Début de l’analyse du système. Cette opération peut nécessiter un certain temps.

Démarrage de la phase de vérification de l’analyse du système.
La vérification 100% est terminée.
La protection des ressources Windows a trouvé des fichiers endommagés, mais
n’a pas réussi à tous les réparer. Des détails sont inclus dans le journal
CBS.Log windir\Logs\CBS\CBS.log. Par exemple C:\Windows\Logs\CBS\CBS.log. Notez que la journalisation n’est pas actuellement
prise en charge dans les scénarios de service hors connexion.

C:\Users\Administrateur>

    Regards,

    0 comments
  4. Docs 15,846 Reputation points
    2021-06-16T11:55:22.947+00:00

    Please change the default language to English:

    https://www.tenforums.com/tutorials/3813-language-add-remove-change-windows-10-a.html
    https://www.tenforums.com/tutorials/136792-change-display-language-windows-10-a.html#option1

    Open administrative command prompt and copy and paste:
    findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

    Find the new text file on the desktop > post a share link

    Run V2 > post a share link into this thread

    https://www.windowsq.com/resources/v2-log-collector.8/
    https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

    .
    .
    .
    .
    .

    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
    .
    .
    .
    .
    .

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.