Windows 10: Issue with dism restorehealth not working

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.900

Image Version: 10.0.18363.1082

[===========================56.8% ]
Error: 14091

The name of an attribute in an identity is not within the legal range.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log



cbs.log error contents


2020-09-27 23:58:41, Info CBS Loaded Servicing Stack v10.0.18362.1073 with Core: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.1073_none_171f6eef2a0feed0\cbscore.dll

2020-09-27 23:58:41, Info CBS Build: 18362.1.amd64fre.19h1_release.190318-1202

2020-09-27 23:58:41, Info CSI 00000001@2020/9/28:03:58:41.337 WcpInitialize: wcp.dll version 10.0.18362.1073 WinBuild.160101.0800

2020-09-27 23:58:41, Info CBS Lock: New lock added: CCbsSessionManager, level: 11, total lock:8

2020-09-27 23:58:41, Info CBS Lock: New lock added: CSIInventoryCriticalSection, level: 64, total lock:9

2020-09-27 23:58:41, Info CBS NonStart: Set pending store consistency check.

2020-09-27 23:58:41, Info CSI 00000002@2020/9/28:03:58:41.348 WcpInitialize: wcp.dll version 10.0.18362.1073 WinBuild.160101.0800

2020-09-27 23:58:41, Info CBS Maint: idle processing paused

2020-09-27 23:58:41, Info CSI 00000003 IAdvancedInstallerAwareStore_ResolvePendingTransactions call 1 flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0x7caaa7dbe0

2020-09-27 23:58:41, Info CSI 00000004 Poqexec successfully registered in [l:12 ml:13]'SetupExecute'

2020-09-27 23:58:41, Info CSI 00000005 CSI Store 2338098821952 initialized

2020-09-27 23:58:42, Error CSI 00000006 F Invalid attribute name found: [l:12]'vursionScope'[gle=0x80004005]

2020-09-27 23:58:42, Error CSI 00000007@2020/9/28:03:58:42.533 F onecore\base\wcp\identity\id_baseidentity.cpp1211: Error STATUS_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME originated in function Windows::Identity::Rtl::Implementation::CRtlIdentityBase::Initialize expression: pBAI != 0

[gle=0x80004005]

2020-09-27 23:58:42, Info CBS Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]

2020-09-27 23:58:42, Info CBS Could not get file name for current session file logging [HRESULT = 0x80004003 - E_POINTER]

2020-09-27 23:58:42, Info CBS Added C:\WINDOWS\Logs\CBS\CBS.log to WER report.

2020-09-27 23:58:42, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20200928034516.log to WER report.

2020-09-27 23:58:42, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20200928033049.cab to WER report.

2020-09-27 23:58:42, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20200909010623.cab to WER report.

2020-09-27 23:58:42, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20200814002704.cab to WER report.

2020-09-27 23:58:42, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20200724224120.cab to WER report.

2020-09-27 23:58:42, Info CBS Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2020-09-27 23:58:42, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2020-09-27 23:58:42, Info CBS Not able to add poqexec.log to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2020-09-27 23:58:42, Info CBS Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2020-09-27 23:58:42, Error CSI 00000008 F STATUS_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME #189415# from Windows::Identity::Rtl::Implementation::CRtlIdentityAuthority::IRtlIdentityAuthority_Parseflags = 0, string = [l:148]'Microsoft-Windows-NewDev, Culture=neutral, Version=10.0.18362.387, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, vursionScope=NonSxS'

[gle=0xd0150017]

2020-09-27 23:58:42, Error CSI 00000009 F HRESULT_FROM_WIN3214091 #188950# from Windows::ServicingAPI::CEnumCSI_COMPONENT::IEnumCSI_COMPONENT_Next...[gle=0x8007370b]

:)

 

How to get damn DISM to work?

Yes, I have the image mounted, the same bloody image I've used to install the OS I'm just using. This is absurd. I've tried this:

Dism /Online /Cleanup-Image /RestoreHealth /Source:E:\x64\sources\install.esd
Dism /Online /Cleanup-Image /RestoreHealth /Source:E:\x64\sources\install.esd:1
Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:E:\x64\sources\install.esd
Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:E:\x64\sources\install.esd /limitaccess
Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:E:\x64\sources\install.esd:1
Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:E:\x64\sources\install.esd:1 /limitaccess

None of this crap works even though entire freaking internet is saying that this is the way to do it. Some even mention using quotas for the path which makes no difference (It doesn't need it anyway since there aren't any spaces anyway.

I just can't understand how can OS integrity check tool feature be dumber as years pass by instead of being smarter and more useful.

EDIT:
Redownloading 4 gigs of stupid image because the one I have apparently isn't good enough. *sigh*

 

Error DISM restorehealth

Hello i just registered after i read all the pages...so opencl.dll is a problem of a windows update? Because i had no issues running sfc/scannow last month
**UPDATE**
Thanks it worked perfectly fine and it fixed any corrupted files.This worked perfectly...it was giving me a headache.Step 3 option 2 converted .esd file to .wim...! Thanks again guys.
step 1 delete current dism and cbs log files
step 2 run Image_Health.cmd - option 1 = scanhealth
step 3 run Image health - option 2 = restorehealth
step 4 run image health - option 3 = restorehealth /source (OPTIONAL because step 3 already fixed the issue)

 

How to get damn DISM to work?

Well, i browsed to the sub directory containing the install.esd file and initiated the following command (one of your previous command)

Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:install.esd:1





it worked as expected