[SOLVED] Windows 10 CBS_E_INVALID_PACKAGE

[axe0]

Hi,

I just installed the August patches and ran SFC.
SFC gave no errors, but as I was a little curious I went through the CBS log that I let Windows create after SFC was done.
After I went through the CBS log I found this, I'm wondering if this may be a serious issue or not.

2016-08-09 21:15:58, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2016-08-09 21:15:58, Info                  CBS    Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2016-08-09 21:15:58, Info                  CBS    Session: 30536306_1973461555 initialized by client WindowsUpdateAgent, external staging directory: (null)
2016-08-09 21:15:58, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2016-08-09 21:15:58, Info                  CBS    Failed to OpenPackage using worker session [HRESULT = 0x800f0805]

Here is the full CBS log.
View attachment cbs.zip

 

[tom982]

Hi axe0,

Those errors are nothing to worry about and can be ignored - you'll see them even on a fresh install of Windows.

SFC did in fact give an error:

2016-08-09 21:21:47, Info                  CSI    000051da [SR] Repairing 1 components2016-08-09 21:21:47, Info                  CSI    000051db [SR] Beginning Verify and Repair transaction
2016-08-09 21:21:47, Info                  CSI    000051dc Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-08-09 21:21:47, Info                  CSI    000051dd [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-08-09 21:21:47, Info                  CSI    000051de@2016/8/9:19:21:47.600 Primitive installers committed for repair
2016-08-09 21:21:47, Info                  CSI    000051df Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-08-09 21:21:47, Info                  CSI    000051e0 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-08-09 21:21:47, Info                  CSI    000051e1 [SR] This component was referenced by [l:125]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10586.0.RemoteFX clientVM and UMTS files and regkeys"
2016-08-09 21:21:47, Info                  CSI    000051e2 Hashes for file member \??\C:\WINDOWS\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-08-09 21:21:47, Info                  CSI    000051e3 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-08-09 21:21:47, Info                  CSI    000051e4 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted

However this can be safely ignored as it's not actually corrupt and is instead an NVIDIA file replacing the Windows one. If it's bothering you, or causing any issues (it's not known to), then you can fix it with this guide:

https://www.sysnative.com/forums/wi...tion-sfc-dism-windows-10-update-1511-th2.html

Tom

 

[axe0]

Thanks Tom, good to hear about those errors :)

I'm fortunately aware of the opencl.dll issue, but I do not have anything from Nvidia.
This makes me wonder where the issue comes from, I don't have a GPU (yet) nor installed/connected anything from Nvidia.