Windows 2019 Failed boot after CU

sysnpb

New member
Joined
Jul 9, 2021
Posts
1
Hi, after of (any) cumulative update - my Windows server 2019 will not boot and there is no option to fix this. CU will install successfully but after that server will not boot.

What i did:

sfc /scannow
dism with restorehealth (without or with source from iso or mount dir ), startcomponentcleanup and startcomponentcleanup with resetbase
chkdsk /r
reset WU components (i used wureset tool)
check registry (i used wureset tool)

After analysis logs i found this:

Warning: Unable to repair payload file
Hashes for file member [l:18] do not match.

This error shown for 67 files.

______________________________________________________________________________________________________________________________________________
Get-ComputerInfo

WindowsBuildLabEx : 17763.1.amd64fre.rs5_release.180914-1434
WindowsCurrentVersion : 6.3
WindowsEditionId : ServerStandard
WindowsInstallationType : Server
WindowsProductName : Windows Server 2019 Standard
WindowsRegisteredOrganization :
WindowsRegisteredOwner : Windows User
WindowsSystemRoot : C:\Windows
WindowsVersion : 1809
BiosBIOSVersion : {VRTUAL - 1, Hyper-V UEFI Release v4.0, Microsoft - 100032}
CsChassisBootupState : Safe
CsChassisSKUNumber : Virtual Machine
CsCurrentTimeZone : 120
CsDaylightInEffect : True
CsDescription : AT/AT COMPATIBLE
CsDNSHostName : XXXX
CsDomain : XXXX
CsDomainRole : MemberServer
CsEnableDaylightSavingsTime : True
CsFrontPanelResetStatus : Unknown
CsHypervisorPresent : True
CsInfraredSupported : False
CsSystemFamily : Virtual Machine
OsName : Microsoft Windows Server 2019 Standard
OsType : WINNT
OsOperatingSystemSKU : StandardServerEdition
OsVersion : 10.0.17763
OsCSDVersion :
OsBuildNumber : 17763
OsBootDevice : \Device\HarddiskVolume2
OsSystemDevice : \Device\HarddiskVolume4
OsSystemDirectory : C:\Windows\system32
OsSystemDrive : C:
OsWindowsDirectory : C:\Windows
OsCountryCode : 48
OsCurrentTimeZone : 120
OsLocaleID : 0415
OsLocale : pl-PL
OsLocalDateTime : 10.07.2021 01:19:46
OsLastBootUpTime : 09.07.2021 23:10:00
OsUptime : 02:09:45.8781374
OsBuildType : Multiprocessor Free
OsCodeSet : 1250
OsDataExecutionPreventionAvailable : True
OsDataExecutionPrevention32BitApplications : True
OsDataExecutionPreventionDrivers : True
OsDataExecutionPreventionSupportPolicy : OptIn
OsPagingFiles : {C:\pagefile.sys}
OsHardwareAbstractionLayer : 10.0.17763.1790
OsServicePackMajorVersion : 0
OsServicePackMinorVersion : 0
OsStatus : OK
OsSuites : {TerminalServices}
OsServerLevel : FullServer
HyperVisorPresent : True
DeviceGuardSmartStatus : Off


________________________________________________________________________________________________________________________________________
Get-Hotfix

HotFixID InstalledBy InstalledOn
------ ----------- -------- ----------- -----------
XXX Update KB4598300
XXX Update KB4486153
XXX Security Update KB4512577
XXX Security Update KB4535680
XXX Security Update KB4580325
XXX Security Update KB4598480
XXX Security Update KB4601393
XXX Security Update KB5000859
XXX Security Update KB5001404
XXX Security Update KB5003243
XXX Security Update KB5000822





_______________________________________________________________________________________________________________________________________________
SFCFix version 3.0.2.1 by niemiro.
Start time: 2021-07-10 00:39:48.086
Microsoft Windows Server 10 Insider Slow, Build 17763 - amd64
Not using a script file.

AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.

Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2021-07-10 01:03:20.147
----------------------EOF-----------------------

I will be grateful for your help.
 

Attachments

Hello,

As you will know some of our helpers have increased workloads professionally, and this has resulted in a slower response time for Windows Update threads.

I am checking to see if you still need help with this thread. If so please respond and this will bring your thread to our attention again. Thank you for your patience.
 

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

Back
Top