pitrack_1
1 Copper

Dell XPS13: Possible corrupt Win 10 Pro installation + installation partition

Issue: errors returned by sfc and dism on a clean install. Errors are not self-repairable, requiring manual intervention. Errors are still present immediately after a clean install (i.e. reset to factory image) indicating likely presence in the factory image files/partition.

 

Intro

Hi,

 I think I have discovered my XPS 13 Win 10 Pro factory install and install partition may contain corrupted windows files. This may affect others too.

You may wish to run the commands below and see if you obtain similar results. If so perhaps you should contact Dell. I did, and service said they were going to send me a USB stick with a factory refresh to redo the SSD, but 2 hrs later phoned me back to say all the USBs had been recalled and it would be a few weeks- make of that what you will about the USB fix sticks…

The system I have is an April ’16 delivered XPS13 with Win10Pro, 8GB, 256Gb SSD, HD (1920x1080) non-touchscreen.

---/ A partial resolution will appear in my next post /---

Description

Here’s a synopsis of what I did to discover the issue. My next post includes a (partial) resolution.

After receiving my XPS13 and setting it up, I uninstalled Mcafee and installed Comodo Personal Firewall and Avira Personal Antivirus, plus Google Chrome and Mozilla Firefox and Citrix Receiver. I connected to my workplace internet, then to home and a relative’s internet. After a few days of gentle internet use I finally obtained a USB key to create the restore backup to. Unfortunately when I tried to initiate this it hung whilst setting up. Looked up online, nothing specific. Not knowing much about Win10 (last O/S at home is XP!) I looked up how to do system checks, finding SFC- which I was rather unfamiliar with except by name- and DISM, which I was totally unfamiliar with even by name.

 

I ran both and was concerned to find either errors or hangs. I looked up and found the log files and searched for errors. In fact the PC started showing signs of problems such as delays, slightly strange responses and particularly, Cortana/search starting actually ‘losing’ results- just before I rebooted it returned ‘nothing found’ to a search for the word ‘reset’ (or perhaps ‘restore’)- luckily I was at work so looked things up on my work PC!

 

The commands I ran to try to repair (garnered from online) were

Sfc /scannow

DISM /online /Cleanup-Image /RestoreHealth

 

At this point, and with nothing of major substance on the laptop, I decided to do a factory reinstall. Looked up the instructions- reboot, press F12 repeatedly and select troubleshoot -> factory Image restore (If I remember rightly). At any rate, it warns you about wiping all and reformatting the drive, which I proceeded with

Once done I completed the Windows setup again, and before I did anything else opened an Admin command window and ran sfc and then dism again. I may have had to connect to the internet first for registration, I can’t remember- but did no more than Win10 required to get started. Both sfc and dism returned the same errors as before, I have listed examples below.

Windows version reported is: v10.0.10586.0

The problem file is: opencl.dll

The problem is: opencl.dll is corrupted and can’t be restored from the store as that file is corrupted.

It seems to be unable to restore from online either. Below are example errors from the two commands and their respective log files, searching for “opencl.dll” should find relevant lines:

Sfc /scannow

-        Ends unable to repair error (or can crash)

-        Log file located at: %windir%\Logs\CBS

------------------------------------------------------------------------------------------------------------------------------------

2016-04-10 22:33:43, Info                 CSI   00003d56 [SR] Verify complete

2016-04-10 22:33:43, Info                 CSI   00003d57 [SR] Verifying 100 (0x0000000000000064) components

2016-04-10 22:33:43, Info                 CSI   00003d58 [SR] Beginning Verify and Repair transaction

2016-04-10 22:33:44, Info                 CSI   00003d59 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-04-10 22:33:44, Info                  CSI   00003d5a [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

------------------------------------------------------------------------------------------------------------------------------------

 

Dism /Cleanup-Image /RestoreHealth /online

-        I believe I used the line above, although the log file reports

-        Exits with an error

-        Log file locate at: %windir%\Logs\DISM

------------------------------------------------------------------------------------------------------------------------------------

2016-04-10 23:48:07, Info                 DISM   DISM Package Manager: PID=7748 TID=736 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine

2016-04-10 23:48:07, Info                 DISM   DISM Package Manager: PID=7748 TID=736 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine

2016-04-10 23:48:07, Info                 DISM   DISM Package Manager: PID=7748 TID=736 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine

2016-04-10 23:48:07, Info                 DISM   DISM Package Manager: PID=7748 TID=736 CBS session options=0x48100! - CDISMPackageManager::Internal_Finalize

2016-04-10 23:50:22, Info                 DISM   DISM Package Manager: PID=7748 TID=5256 Error in operation: source for package or file not found, ResolveSource() unsuccessful. (CBS HRESULT=0x800f081f) - CCbsConUIHandler::Error

2016-04-10 23:50:22, Error                 DISM   DISM Package Manager: PID=7748 TID=736 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)

2016-04-10 23:50:22, Error                 DISM   DISM Package Manager: PID=7748 TID=736 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg

2016-04-10 23:50:22, Error                 DISM   DISM Package Manager: PID=7748 TID=736 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)

2016-04-10 23:50:22, Error                 DISM   DISM Package Manager: PID=7748 TID=736 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg

2016-04-10 23:50:22, Error                 DISM   DISM Package Manager: PID=7748 TID=736 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800f081f)

2016-04-10 23:50:22, Error                 DISM   DISM Package Manager: PID=7748 TID=736 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)

2016-04-10 23:50:22, Info                 DISM   DISM Package Manager: PID=7748 TID=736 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine

2016-04-10 23:50:22, Info                 DISM   DISM Provider Store: PID=7748 TID=736 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

2016-04-10 23:50:22, Info                 DISM   DISM Provider Store: PID=7748 TID=736 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

2016-04-10 23:50:22, Info                 DISM   DISM Provider Store: PID=7748 TID=736 Found the PE Provider. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

2016-04-10 23:50:22, Info                 DISM   DISM Provider Store: PID=7748 TID=736 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider

2016-04-10 23:50:22, Info                 DISM   DISM Package Manager: PID=7748 TID=736 Finalizing CBS core. - CDISMPackageManager::Finalize

2016-04-10 23:50:22, Info                 DISM   DISM Provider Store: PID=7748 TID=736 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

2016-04-10 23:50:22, Info                 DISM   DISM Manager: PID=7204 TID=5028 Closing session event handle 0x16c - CDISMManager::CloseImageSession

2016-04-10 23:50:23, Info                DISM   DISM.EXE: Image session has been closed. Reboot required=no.

2016-04-10 23:50:23, Info                 DISM   DISM.EXE:

2016-04-10 23:50:23, Info                 DISM   DISM.EXE: <----- Ending Dism.exe session ----->

2016-04-10 23:50:23, Info                 DISM   DISM.EXE:

2016-04-10 23:50:23, Info                 DISM   DISM Provider Store: PID=7204 TID=5028 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

2016-04-10 23:50:23, Info                 DISM   DISM Provider Store: PID=7204 TID=5028 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider

2016-04-10 23:50:23, Info                 DISM   DISM Provider Store: PID=7204 TID=5028 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

------------------------------------------------------------------------------------------------------------------------------------

 Conclusions

AS it happened directly after a clean install, I assume it has installed with corrupted files. This means the install image is itself defective.

 

Now Dell were unable to provide me with a resolution for this, however they have contacted me back and appear to be currently investigating it. I looked up the issue and dll online and found others with the issue. I have resolved the issue myself and the resolution may be found online- I will include it in my next post. This resolution will fix the currently installed version HOWEVER it will not fix the factory image or restore partition, meaning if you do a factory refresh you will have the problem back again.

 

I must say that given my build likely comes off some bulk build somewhere then it’s possible that there is a corrupt install going around. This either points to:

- a lack of Quality Control (I mean, really! Microsoft’s own diagnostics telling you the installed system is not right and it still being released?)

- or a knowing release of a corrupted OS (one hopes not)…

Note a partial resolution appears in my next post shortly...

_______

Patrick.

5 Replies
pitrack_1
1 Copper

RE: Dell XPS13: Possible corrupt Win 10 Pro installation + installation partition

RESOLUTION OF THE WIN 10 INSTALL OPENCL.DLL CORRUPTION ISSUE

Synopsis

The resolution is simple, if a slightly involved to carry out: You need to optain a copy of a valid opencl.dll in a valid Windows image and point sfc or dism to this image without recourse to elsewhere. This requires a ~6-7Gb download of the relevant windows image for your computer (you’ll need the windows version, e.g. 10.0.10586 and I hope you don’t require two e.g. for 64/32-bit!) then direction of the programs to use that file.

 

Basic Instructions

The instructions basically are as follows:

1)     Download the relevant windows file for your PC from http://www.microsoft.com/en-us/software-download/techbench

  1. You should use the Windows 10 selection (K and KN refer to Euro and Korean versions due to legal issues)

2)     Save the ISO disk image to an easily accessible position, e.g. c:\temp\win10iso\

3)     Mount the ISO (right click-it in Explorer and select Mount, it should choose the next accessible drive letter, e.g. 😧 in my case)

4)     Open an Admin command prompt

5)     Run the command:

“DISM /Online /Cleanup-Image /RestoreHealth /source:wim:<path-to-install.wim file>:1 /limitaccess”

Where <path-to-install.wim file>:1 is something like: /Source:wim:d:\sources\install.wim:1

So in my case the command was

“Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:d:\sources\install.wim:1 /limitaccess”

6)     Run sfc /scannow again

7)     Restart the PC

😎     When the pc has restarted,

  1. again open an Admin command prompt
  2. run sfc /scannow and
  3. dism /online /Cleanup-Image /ScanHealth

No errors should be returned by SFC and DISM. If you search the log files for opencl.dll the prior (fix) ones should show corruptions detected and fixes applied, the log files after the reboot should show no returns to find for öpencl.dll” as there is no longer a problem.

Instruction Links

Instructions to do this (or variants thereof, couldn’t find my exact reference from before) may be found at (my brief ones are below)

http://www.tenforums.com/performance-maintenance/23654-error-dism-restorehealth-2.html

https://social.technet.microsoft.com/Forums/en-US/85680348-c2c4-40bc-9f39-9dcfeea331c0/windows-10-op... and scan down for “I solved it like this, Sir.”

http://www.tenforums.com/performance-maintenance/29947-sfc-some-corrupt-files-can-not-fixed.html

 

File locations

Windows ISO can be obtained from

http://www.microsoft.com/en-us/software-download/techbench

 

Hope this helps!

 

Patrick.

 

_______

Patrick.

0 Kudos
Moderator
Moderator

RE: Dell XPS13: Possible corrupt Win 10 Pro installation + installation partition

PITRACK_1,

Thank you for posting this information. I apologize for the issues you have experienced with Windows 10. I have sent this information to our OS engineering team. 

0 Kudos
pitrack_1
1 Copper

RE: Dell XPS13: Possible corrupt Win 10 Pro installation + installation partition

Jesse L,

thanks for your reply. I have liaised with a team member in Australia (think you call 'em ANZ ) and sent him the log files from SFC and DISM tonight (sorry, now this morning here!) so hopefully there's some technical info in there to assist with resolution of this issue.

We've (wife & I) put nothing on this system of any worth yet so another clean reinstall is not a major issue. Luckily we're home users not road warriors or a sole trader who may be dependent on it.

I haven't tried another a restore backup to a USB stick yet, that's next on the list.

Apart from this I'm happy with the XPS13 unit and astounded by the battery life compared to what I'm used to previously.

Cheers,

Patrick.

_______

Patrick.

0 Kudos
Moderator
Moderator

RE: Dell XPS13: Possible corrupt Win 10 Pro installation + installation partition

pitrack_1,

Thank You!

0 Kudos
DaisyDawson
1 Copper

RE: Dell XPS13: Possible corrupt Win 10 Pro installation + installation partition

Dear pitrack_1

I have had a similar issue with Windows 10 updates not installing. After much time with Microsoft tech, I got the following email:

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

This is AAAAA from Microsoft escalation team. We had a conversation regarding the case number:

<ADMIN NOTE: service request number removed per privacy policy>,

and we tried to Upgrade to the Anniversary update using the ISO, but unfortunately it failed with the error

"We could'nt update the system reserved partition" .

So we would not be able to Extend the system reserved partion as we do not have the access and it needs to be done by Computer manufacturer.

So please conatct Dell and ask them to Extend the system reserved partion.

Thank you!

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

So, Microsoft can't change the system reserved partition which needs to be increased to accommodate the upgrade.

Does your solution apply to my situation?

XPS 13 9343, 8GM RAM, 256 SDD, upgraded to Windows 10 after purchasing laptop.

Thank you,

0 Kudos