Dear all,
I have a problem when running the command line 'dism /online /cleanup-image /restorehealth'.
Before running into this problem, my computer was unstable / halted several times due to voltage problem, and I have done several cycles of 'chkdsk C: /f /x /v -> dism /online /cleanup-image /restorehealth -> sfc /scannow'.
Later on, it was found that the NlsData0000.dll in %windir%\SysWOW64 was corrupted (as it turns out, it was a MS fault which many Windows Server 2016 owners have faced for the last few months), and I have manually repaired it (as the sfc /scannow failed to replace it with the correct file within the WinSXS store) by copying the file NlsData0000.dll from the directory C:\Windows\WinSxS\x86_microsoft-windows-naturallanguage6-base_31bf3856ad364e35_10.0.14393.2368_none_6a7cd8f8f7b64c5d to %windir%\SysWOW64. And I have checked the SHA256 hash is the correct one for the new file based on following lines in CBS.log.
After I have repaired the file, I have rebooted the machine again, and was performing the cycle of 'chkdsk C: /f /x /v -> dism /online /cleanup-image /restorehealth -> sfc /scannow'. But this time the computer halted when performing sfc /scannow, so I have no option but have to hard reset the machine.
After I have hard reset the machine, I tried to run another cycle of 'chkdsk C: /f /x /v -> dism /online /cleanup-image /restorehealth -> sfc /scannow' again. But this time the 'dism /online /cleanup-image /restorehealth' has shown the following messages instead.
To be honest, I have been using a ramdisk for storing temporary files (i.e. temp folder located on ramdisk). But even I have used the physical disk for the above command with the dism parameter '/ScratchDir' or by disabling the ramdisk, the above message still appears on the screen.
After looking into the CBS.log, I have found the followings lines that are most relevant.
And if I run the sfc /scannow again, the following lines are shown on the CBS.log.
So I just want to ask for few things first in order to fix the current problem.
1. Can someone tell me what is the reason / how to fix the 'Current tick count lower than last tick count. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]' problem? If I remember correctly, this problem should be related to CBS registry.
2. Can someone tell me why there is an E_OUTOFMEMORY error (I have 32GB of RAM and 6 GB dedicated for ramdisk, erorr occurs even the ramdisk is disabled) and how I fix it?
3. Why the x86 WinSXS folder is having a different NlsData0000.dll when compared to the WOW64 arch? (I saw their version number is different as well)
I have enclosed the CBS log (both old and new one) for your reference. Thank you in advance for any answer.
I have a problem when running the command line 'dism /online /cleanup-image /restorehealth'.
Before running into this problem, my computer was unstable / halted several times due to voltage problem, and I have done several cycles of 'chkdsk C: /f /x /v -> dism /online /cleanup-image /restorehealth -> sfc /scannow'.
Later on, it was found that the NlsData0000.dll in %windir%\SysWOW64 was corrupted (as it turns out, it was a MS fault which many Windows Server 2016 owners have faced for the last few months), and I have manually repaired it (as the sfc /scannow failed to replace it with the correct file within the WinSXS store) by copying the file NlsData0000.dll from the directory C:\Windows\WinSxS\x86_microsoft-windows-naturallanguage6-base_31bf3856ad364e35_10.0.14393.2368_none_6a7cd8f8f7b64c5d to %windir%\SysWOW64. And I have checked the SHA256 hash is the correct one for the new file based on following lines in CBS.log.
Code:
2018-09-09 19:06:09, Info CSI 00011eda [SR] Verify complete
2018-09-09 19:06:09, Info CSI 00011edb [SR] Repairing 1 components
2018-09-09 19:06:09, Info CSI 00011edc [SR] Beginning Verify and Repair transaction
2018-09-09 19:06:09, Info CSI 00011edd Hashes for file member \??\C:\Windows\SysWOW64\NlsData0000.dll do not match actual file [l:15]'NlsData0000.dll' :
Found: {l:32 VqGFDDtNkUJL2y72172gbrdibqg7T6Y8qeCjl1AgmkA=} Expected: {l:32 zswq09s5+Zb0OfXSW1ikcF7tHaaSH36DU+P1teqdh3g=}
2018-09-09 19:06:09, Info CSI 00011ede [SR] Repairing corrupted file \??\C:\Windows\SysWOW64\NlsData0000.dll from store
2018-09-09 19:06:09, Info CSI 00011edf File [l:15]'NlsData0000.dll' in [l:23]'\??\C:\Windows\SysWOW64' switching ownership
Old: Microsoft-Windows-NaturalLanguage6-base, version 10.0.14393.2368, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}
New: Microsoft-Windows-NaturalLanguage6-base, version 10.0.14393.2368, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2018-09-09 19:06:09, Info CSI 00011ee0@2018/9/9:11:06:09.934 Primitive installers committed for repair
2018-09-09 19:06:09, Info CSI 00011ee1 [SR] Repair complete
2018-09-09 19:06:09, Info CSI 00011ee2 [SR] Committing transactionAfter I have repaired the file, I have rebooted the machine again, and was performing the cycle of 'chkdsk C: /f /x /v -> dism /online /cleanup-image /restorehealth -> sfc /scannow'. But this time the computer halted when performing sfc /scannow, so I have no option but have to hard reset the machine.
After I have hard reset the machine, I tried to run another cycle of 'chkdsk C: /f /x /v -> dism /online /cleanup-image /restorehealth -> sfc /scannow' again. But this time the 'dism /online /cleanup-image /restorehealth' has shown the following messages instead.
Code:
Deployment Image Servicing and Management tool
Version: 10.0.14393.0
Image Version: 10.0.14393.0
[==========================100.0%==========================]
Error: 14
Not enough storage is available to complete this operation.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.logTo be honest, I have been using a ramdisk for storing temporary files (i.e. temp folder located on ramdisk). But even I have used the physical disk for the above command with the dism parameter '/ScratchDir' or by disabling the ramdisk, the above message still appears on the screen.
After looking into the CBS.log, I have found the followings lines that are most relevant.
Code:
2018-09-12 05:57:43, Info CSI 00000006@2018/9/11:21:57:43.388 Starting corruption detection (InnerFlags=5)
2018-09-12 05:57:43, Info CBS FLOW: Entering stage: CheckCsi
2018-09-12 05:58:50, Info CSI 00000007 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-naturallanguage6-base_31bf3856ad364e35_10.0.14393.2368_none_d0f01ecee4747f8e\NlsData0000.dll do not match actual file [l:15]'NlsData0000.dll' :
Found: {l:32 zswq09s5+Zb0OfXSW1ikcF7tHaaSH36DU+P1teqdh3g=} Expected: {l:32 VqGFDDtNkUJL2y72172gbrdibqg7T6Y8qeCjl1AgmkA=}
2018-09-12 06:06:14, Warning CBS Current tick count lower than last tick count. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2018-09-12 06:06:14, Info CSI 00000008@2018/9/11:22:06:14.748 Corruption detection complete. numCorruptions = 1, Disp = 1.
2018-09-12 06:06:14, Info CBS Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.
2018-09-12 06:06:14, Info CSI 00000009@2018/9/11:22:06:14.748 CSI Transaction @0x275107e5a10 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000000 and client id 'TI5.30689818_1522281700:1/'
2018-09-12 06:06:14, Info CSI 0000000a@2018/9/11:22:06:14.748 CSI Transaction @0x275107e5a10 destroyed
2018-09-12 06:06:14, Info CBS Repr: CSI Store check completes
2018-09-12 06:06:14, Info CBS Exec: Download qualification evaluation, business scenario: Manual Corruption Repair
2018-09-12 06:06:14, Info CBS Exec: Clients specified using Windows Update.
2018-09-12 06:06:14, Warning CBS Current tick count lower than last tick count. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2018-09-12 06:06:14, Info CBS WU: Microsoft Update service is the default, URL: https://fe2.update.microsoft.com/v6/, Name: Microsoft Update
2018-09-12 06:06:16, Info CBS Session: 30689819_2839665889 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
2018-09-12 06:06:16, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2018-09-12 06:06:16, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2018-09-12 06:06:16, Info CBS Session: 30689819_2839665890 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
2018-09-12 06:06:16, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2018-09-12 06:06:16, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
.............................................................................................................Skipped...................................................................................................
2018-09-12 06:13:35, Info CBS DWLD:Search is done, set download progress to 20 percent.
2018-09-12 06:13:35, Warning CBS Current tick count lower than last tick count. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2018-09-12 06:13:39, Info CBS Failed to get bundled updates [HRESULT = 0x8007000e - E_OUTOFMEMORY]
2018-09-12 06:13:39, Info CBS Failed to check whether the update is required [HRESULT = 0x8007000e - E_OUTOFMEMORY]
2018-09-12 06:13:39, Info CBS Failed to download updates [HRESULT = 0x8007000e - E_OUTOFMEMORY]
2018-09-12 06:13:39, Warning CBS Current tick count lower than last tick count. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2018-09-12 06:13:39, Info CBS Failed to collect payload and there is nothing to repair. [HRESULT = 0x8007000e - E_OUTOFMEMORY]
2018-09-12 06:13:39, Info CBS Failed to repair store. [HRESULT = 0x8007000e - E_OUTOFMEMORY]
2018-09-12 06:13:39, Info CBS Ensure CBS corruption flag is clear
2018-09-12 06:13:39, Info CBS
=================================
Checking System Update Readiness.
(p) CSI Payload Corrupt wow64_microsoft-windows-naturallanguage6-base_31bf3856ad364e35_10.0.14393.2368_none_d0f01ecee4747f8e\NlsData0000.dll
Repair failed: Missing replacement payload.
(w) CBS Package Index Package Missing 0x80070490 Package_1847_for_KB4056890~31bf3856ad364e35~amd64~~0.0.0.0 Package_1847_for_KB4056890~31bf3856ad364e35~amd64~~10.0.1.8
Summary:
Operation: Detect and Repair
Operation result: 0x8007000e
Last Successful Step: Entire operation completes.
Total Detected Corruption: 2
CBS Manifest Corruption: 0
CBS Metadata Corruption: 1
CSI Manifest Corruption: 0
CSI Metadata Corruption: 0
CSI Payload Corruption: 1
Total Repaired Corruption: 0
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 0
CSI Store Metadata refreshed: True
Total Operation Time: 1004 seconds.
2018-09-12 06:13:39, Info CBS CheckSur: hrStatus: 0x8007000e [E_OUTOFMEMORY], download Result: 0x800f0948 [CBS_E_SOURCE_MISSING_FROM_WU_CAB]
2018-09-12 06:13:39, Info CBS Count of times corruption detected: 1
2018-09-12 06:13:39, Info CBS Seconds between initial corruption detections: -1
2018-09-12 06:13:39, Info CBS Seconds between corruption and repair: -1
2018-09-12 06:13:39, Info CBS SQM: Package change report datapoints not populated because SQM is not initialized or not running online.
2018-09-12 06:13:39, Info CBS Failed to run Detect and repair. [HRESULT = 0x8007000e - E_OUTOFMEMORY]
2018-09-12 06:13:39, Info CBS Reboot mark cleared
2018-09-12 06:13:39, Info CBS Winlogon: Simplifying Winlogon CreateSession notifications
2018-09-12 06:13:39, Info CBS Winlogon: Deregistering for CreateSession notifications
2018-09-12 06:13:39, Info CBS Exec: Processing complete, session(Corruption Repairing): 30689818_1522281700 [HRESULT = 0x8007000e - E_OUTOFMEMORY]
2018-09-12 06:13:39, Error CBS Session: 30689818_1522281700 failed to perform store corruption detect and repair operation. [HRESULT = 0x8007000e - E_OUTOFMEMORY]
2018-09-12 06:13:39, Info CBS Session: 30689818_1522281700 finalized. Download error: 0x8007000e [E_OUTOFMEMORY], Reboot required: no [HRESULT = 0x8007000e - E_OUTOFMEMORY]
2018-09-12 06:13:39, Info CBS Failed to FinalizeEx using worker session [HRESULT = 0x8007000e]
2018-09-12 06:15:40, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2018-09-12 06:15:40, Info CBS TiWorker signaled for shutdown, going to exit.
2018-09-12 06:15:40, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2018-09-12 06:15:40, Info CBS Ending the TiWorker main loop.
2018-09-12 06:15:40, Info CBS Starting TiWorker finalization.
2018-09-12 06:15:40, Info CBS CbsCoreFinalize: ManifestCacheFinalize
2018-09-12 06:15:40, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2018-09-12 06:15:40, Info CBS CbsCoreFinalize: ComponentAnalyzerFinalize
2018-09-12 06:15:40, Info CBS CbsCoreFinalize: PackageTrackerFinalize
2018-09-12 06:15:40, Info CBS CbsCoreFinalize: CoreResourcesUnload
2018-09-12 06:15:40, Info CBS CbsCoreFinalize: SessionManagerFinalize
2018-09-12 06:15:40, Info CBS CbsCoreFinalize: CapabilityManagerFinalize
2018-09-12 06:15:40, Info CBS CbsCoreFinalize: PublicObjectMonitorFinalize
2018-09-12 06:15:40, Info CBS CbsCoreFinalize: Enter vCoreInitializeLock
2018-09-12 06:15:40, Info CBS CbsCoreFinalize: WcpUnload
2018-09-12 06:15:40, Info CBS CbsCoreFinalize: DrupUnload
2018-09-12 06:15:40, Info CBS CbsCoreFinalize: CfgMgr32Unload
2018-09-12 06:15:40, Info CBS CbsCoreFinalize: DpxUnload
2018-09-12 06:15:40, Info CBS CbsCoreFinalize: CbsEsdUnload
2018-09-12 06:15:40, Info CBS CbsCoreFinalize: CbsTraceInfoUninitialize
2018-09-12 06:15:40, Info CBS CbsCoreFinalize: CbsEventUnregister
2018-09-12 06:15:40, Info CBS CbsCoreFinalize: AppContainerUnload
2018-09-12 06:15:40, Info CBS CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2018-09-12 06:15:40, Info CBS Ending TiWorker finalization.
2018-09-12 06:17:54, Info CBS Ending the TrustedInstaller main loop.
2018-09-12 06:17:54, Info CBS Starting TrustedInstaller finalization.
2018-09-12 06:17:54, Info CBS Winlogon: Stopping notify server
2018-09-12 06:17:54, Info CBS Winlogon: Unloading SysNotify DLL
2018-09-12 06:17:54, Info CBS Ending TrustedInstaller finalization.And if I run the sfc /scannow again, the following lines are shown on the CBS.log.
Code:
2018-09-12 23:05:16, Info CSI 000076b7 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-naturallanguage6-base_31bf3856ad364e35_10.0.14393.2368_none_d0f01ecee4747f8e\NlsData0000.dll do not match actual file [l:15]'NlsData0000.dll' :
Found: {l:32 zswq09s5+Zb0OfXSW1ikcF7tHaaSH36DU+P1teqdh3g=} Expected: {l:32 VqGFDDtNkUJL2y72172gbrdibqg7T6Y8qeCjl1AgmkA=}
2018-09-12 23:05:16, Info CSI 000076b8 [SR] Cannot repair member file [l:15]'NlsData0000.dll' of Microsoft-Windows-NaturalLanguage6-base, version 10.0.14393.2368, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
.............................................................................................................Skipped...................................................................................................
2018-09-12 23:05:18, Info CSI 00007725 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-naturallanguage6-base_31bf3856ad364e35_10.0.14393.2368_none_d0f01ecee4747f8e\NlsData0000.dll do not match actual file [l:15]'NlsData0000.dll' :
Found: {l:32 zswq09s5+Zb0OfXSW1ikcF7tHaaSH36DU+P1teqdh3g=} Expected: {l:32 VqGFDDtNkUJL2y72172gbrdibqg7T6Y8qeCjl1AgmkA=}
2018-09-12 23:05:18, Info CSI 00007726 [SR] Cannot repair member file [l:15]'NlsData0000.dll' of Microsoft-Windows-NaturalLanguage6-base, version 10.0.14393.2368, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2018-09-12 23:05:18, Info CSI 00007727 [SR] This component was referenced by [l:82]'Package_8695_for_KB4343887~31bf3856ad364e35~amd64~~10.0.1.10.4343887-18718_neutral'
2018-09-12 23:05:18, Info CSI 00007728 Hashes for file member \??\C:\Windows\SysWOW64\NlsData0000.dll do not match actual file [l:15]'NlsData0000.dll' :
Found: {l:32 zswq09s5+Zb0OfXSW1ikcF7tHaaSH36DU+P1teqdh3g=} Expected: {l:32 VqGFDDtNkUJL2y72172gbrdibqg7T6Y8qeCjl1AgmkA=}
2018-09-12 23:05:18, Info CSI 00007729 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-naturallanguage6-base_31bf3856ad364e35_10.0.14393.2368_none_d0f01ecee4747f8e\NlsData0000.dll do not match actual file [l:15]'NlsData0000.dll' :
Found: {l:32 zswq09s5+Zb0OfXSW1ikcF7tHaaSH36DU+P1teqdh3g=} Expected: {l:32 VqGFDDtNkUJL2y72172gbrdibqg7T6Y8qeCjl1AgmkA=}
2018-09-12 23:05:18, Info CSI 0000772a [SR] Could not reproject corrupted file \??\C:\Windows\SysWOW64\NlsData0000.dll; source file in store is also corrupted
2018-09-12 23:05:18, Info CSI 0000772b@2018/9/12:15:05:18.712 Primitive installers committed for repair
2018-09-12 23:05:18, Info CSI 0000772c@2018/9/12:15:05:18.730 Primitive installers committed for repair
.............................................................................................................Skipped...................................................................................................
2018-09-12 23:09:13, Info CSI 00008fb1 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-naturallanguage6-base_31bf3856ad364e35_10.0.14393.2368_none_d0f01ecee4747f8e\NlsData0000.dll do not match actual file [l:15]'NlsData0000.dll' :
Found: {l:32 zswq09s5+Zb0OfXSW1ikcF7tHaaSH36DU+P1teqdh3g=} Expected: {l:32 VqGFDDtNkUJL2y72172gbrdibqg7T6Y8qeCjl1AgmkA=}
2018-09-12 23:09:13, Info CSI 00008fb2 [SR] Cannot repair member file [l:15]'NlsData0000.dll' of Microsoft-Windows-NaturalLanguage6-base, version 10.0.14393.2368, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2018-09-12 23:09:13, Info CSI 00008fb3@2018/9/12:15:09:13.835 Primitive installers committed for repair
2018-09-12 23:09:13, Info CSI 00008fb4 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-naturallanguage6-base_31bf3856ad364e35_10.0.14393.2368_none_d0f01ecee4747f8e\NlsData0000.dll do not match actual file [l:15]'NlsData0000.dll' :
Found: {l:32 zswq09s5+Zb0OfXSW1ikcF7tHaaSH36DU+P1teqdh3g=} Expected: {l:32 VqGFDDtNkUJL2y72172gbrdibqg7T6Y8qeCjl1AgmkA=}
2018-09-12 23:09:13, Info CSI 00008fb5 [SR] Cannot repair member file [l:15]'NlsData0000.dll' of Microsoft-Windows-NaturalLanguage6-base, version 10.0.14393.2368, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2018-09-12 23:09:13, Info CSI 00008fb6 [SR] This component was referenced by [l:82]'Package_8695_for_KB4343887~31bf3856ad364e35~amd64~~10.0.1.10.4343887-18718_neutral'
2018-09-12 23:09:13, Info CSI 00008fb7 Hashes for file member \??\C:\Windows\SysWOW64\NlsData0000.dll do not match actual file [l:15]'NlsData0000.dll' :
Found: {l:32 zswq09s5+Zb0OfXSW1ikcF7tHaaSH36DU+P1teqdh3g=} Expected: {l:32 VqGFDDtNkUJL2y72172gbrdibqg7T6Y8qeCjl1AgmkA=}
2018-09-12 23:09:13, Info CSI 00008fb8 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-naturallanguage6-base_31bf3856ad364e35_10.0.14393.2368_none_d0f01ecee4747f8e\NlsData0000.dll do not match actual file [l:15]'NlsData0000.dll' :
Found: {l:32 zswq09s5+Zb0OfXSW1ikcF7tHaaSH36DU+P1teqdh3g=} Expected: {l:32 VqGFDDtNkUJL2y72172gbrdibqg7T6Y8qeCjl1AgmkA=}
2018-09-12 23:09:13, Info CSI 00008fb9 [SR] Could not reproject corrupted file \??\C:\Windows\SysWOW64\NlsData0000.dll; source file in store is also corrupted
2018-09-12 23:09:13, Info CSI 00008fba@2018/9/12:15:09:13.872 Primitive installers committed for repairSo I just want to ask for few things first in order to fix the current problem.
1. Can someone tell me what is the reason / how to fix the 'Current tick count lower than last tick count. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]' problem? If I remember correctly, this problem should be related to CBS registry.
2. Can someone tell me why there is an E_OUTOFMEMORY error (I have 32GB of RAM and 6 GB dedicated for ramdisk, erorr occurs even the ramdisk is disabled) and how I fix it?
3. Why the x86 WinSXS folder is having a different NlsData0000.dll when compared to the WOW64 arch? (I saw their version number is different as well)
I have enclosed the CBS log (both old and new one) for your reference. Thank you in advance for any answer.