[SOLVED] [Win10Home x64] Latest update failed, Start Menu broken, DISM error 193

L

Luxamar

Member
Joined
Apr 12, 2017
Posts
10
Last night, sometime in the wee hours, I received the dreaded Restart window after Windows installed updates automatically. I work the graveyard shift, and it was a slow night, so I decided to go ahead and restart. The update took a little longer than normal, but restarted fine. I logged back in and noticed I could no longer click on the wifi signal indicator. I could right-click it, but left clicking did nothing. Then I realized the Start Menu no longer worked either. Many other baseline Windows functions have also broken. Display Properties no longer opens. A small error box appears after some time if this is attempted. I can attempt to run Settings in the Run box by typing ms-settings: but this also errors out. Control Panel, Services, Task Manager, and Event Viewer all work fine. Third party apps, such as Steam, and games, all work fine.

After some research, I found two threads here with folks experiencing similar issues:

However, after trying many of the same fixes, nothing has helped. Below is a list of everything I have tried.

  1. Normal restart of the computer.
  2. Restart into safe mode.
    1. Someone suggested this elsewhere as a fix.
    2. Start menu still broken in safe mode.
  3. Accessed a different local user profile.
  4. Erased C:\Users\<username>\AppData\Local\TileDataLayer folder and let it rebuild.
    1. When logging on after doing this, the Edge and Windows Store shortcuts pinned to the taskbar turned black, and then disappeared shortly after.
    2. These were two apps affected by the malfunction.
    3. Replaced the folder and the apps are still missing from the taskbar.
    4. Note that Windows Explorer, iTunes, and MSI Dragon are all still there and work fine, though they cannot be right-clicked.
  5. Ran sfc /scannow from elevated PowerShell. Found corrupt files unable to fix. Logs will be attached.
  6. Ran DISM /online /cleanup-image /restorehealth. Error 193
    1. This error appears when doing anything with the /online flag similar to Cybot's post linked above.
    2. This error is the likely issue causing all other problems blocking solutions I tried later.
  7. Ran System Restore to a restore point a few hours earlier after having installed VirtualBox. System Restore failed.
  8. Downloaded and attempted to install Windows 10 Creators Update. This also fails after downloading all its components.
  9. Attempted in-place upgrade with a USB stick of Windows 10 Home. Failed.
  10. Attempted reinstall of Windows, keeping my files but uninstalling apps. Failed. No changes were made to OS.
  11. Went back to DISM and copied a set of DLLs into the C:\Windows\System32\downlevel folder.
    1. This took quite some effort due to file permissions for Administrator accounts being limited to Read and Execute.
    2. The folder and all contained files are now owned by my account. I was able to perform the copy, but DISM still fails to run with error 193.
  12. Ran sfc /scannow, copying the log file in preparation for uploading here.
  13. Ran SFCFix from stickied post. Scan began, and then crashed with the following message:
    1. SFCFix version 3.0.0.0 by niemiro.
      Start time: 2017-04-12 15:03:24.425
      Microsoft Windows 10 Build 14393 - amd64
      Not using a script file.




      SFCFix version 3.0.0.0 by niemiro has encountered an unhandled exception.
      Currently storing 0 datablocks.
      Finish time: 2017-04-12 15:06:03.289
      ----------------------EOF-----------------------


At this point, I have run out of ideas. I want to avoid a factory reset if at all possible. All my research points to SFC and DISM as the integral parts of the problem.

Please advise. This is me at this point: :banghead:
Also, as a reminder, I work the graveyard shift. My replies will return at strange hours!
Thank you for your time.

View attachment 25542
View attachment SFCFix.txt
View attachment dism.zip
 
I have several. One of them has a copy of Windows 10 on it that has plenty of space left over.
 
Let's fix the following ones first.

Code: 
Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-i..codepage-additional_31bf3856ad364e35_10.0.14393.0_none_82d1cf1356a1336c\C_1146.NLS do not match actual file [l:10]'C_1146.NLS' :
Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-i..ell-serviceprovider_31bf3856ad364e35_10.0.14393.0_none_ee7b2ef6f638c0db\windows.immersiveshell.serviceprovider.dll do not match actual file [l:42]'windows.immersiveshell.serviceprovider.dll' :
Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-m..namespace-downlevel_31bf3856ad364e35_10.0.14393.0_none_f4d9462b97ccf242\api-ms-win-service-management-l1-1-0.dll do not match actual file [l:40]'api-ms-win-service-management-l1-1-0.dll' :
Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-smbserver-powershell_31bf3856ad364e35_10.0.14393.0_none_8a802f6ad7df5956\SmbShare.Format.Helper.psm1 do not match actual file [l:27]'SmbShare.Format.Helper.psm1' :
Hashes for file member \SystemRoot\WinSxS\amd64_netr28ux.inf_31bf3856ad364e35_10.0.14393.0_none_6f846fbe3a7d97a0\FW_7662.bin do not match actual file [l:11]'FW_7662.bin' :
Hashes for file member \SystemRoot\WinSxS\amd64_prndlcl1.inf_31bf3856ad364e35_10.0.14393.0_none_b0490a28ff84fa88\deCV5A-PropertyBag.bag do not match actual file [l:22]'deCV5A-PropertyBag.bag' :
Hashes for file member \SystemRoot\WinSxS\amd64_prnsacl1.inf_31bf3856ad364e35_10.0.14393.0_none_f7ab09671067472c\saCV2A-PropertyBag.bag do not match actual file [l:22]'saCV2A-PropertyBag.bag' :
Hashes for file member \SystemRoot\WinSxS\amd64_wnetvsc_vfpp.inf.resources_31bf3856ad364e35_10.0.14393.0_en-us_dc1d16e57d3c9297\wnetvsc_vfpp.inf_loc do not match actual file [l:20]'wnetvsc_vfpp.inf_loc' :
Hashes for file member \SystemRoot\WinSxS\msil_system.web.datavisualization.design_31bf3856ad364e35_4.0.14305.0_none_9e181e42be26a32f\System.Web.DataVisualization.Design.dll do not match actual file [l:39]'System.Web.DataVisualization.Design.dll' :
Hashes for file member \SystemRoot\WinSxS\msil_taskscheduler.resources_31bf3856ad364e35_10.0.14393.0_en-us_f35ef7d4f8f478ca\TaskScheduler.resources.dll do not match actual file [l:27]'TaskScheduler.resources.dll' :
Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-tapicore_31bf3856ad364e35_10.0.14393.0_none_1c02ee5791aa00b9\tapiui.dll do not match actual file [l:10]'tapiui.dll' :
Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-v..ure-filter-tvanalog_31bf3856ad364e35_10.0.14393.0_none_9b09b58982840d70\WSTPager.ax do not match actual file [l:11]'WSTPager.ax' :
Hashes for file member \SystemRoot\WinSxS\wow64_networking-mpssvc-drv.resources_31bf3856ad364e35_10.0.14393.0_en-us_858d650ed0da76d8\mpsdrv.sys.mui do not match actual file [l:14]'mpsdrv.sys.mui' :
Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-m..extension.resources_31bf3856ad364e35_10.0.14393.0_en-us_b5072738a9f086fd\mprext.dll.mui do not match actual file [l:14]'mprext.dll.mui' :

Please do the following.

Extract Files
Save the attached file to your c:\users\public folder.
Then right-click on Files.zip and select Extract All... Keep the default and click Extract.

Replace Files
1. Hold down the Shift button on your keyboard and then restart your computer. Don't let go of the Shift button until the Choose an option screen comes up.
2. Click on Troubleshoot
3. Click on Advanced Options
4. Click on Command Prompt. The machine will restart and prepare your command prompt. You may be prompted to pick your user account and type in a password if you have one. Go ahead and do this if requested.
5. You should eventually end up at a command prompt showing X:\windows\system32>
6. Type each of the following lines and press enter after each
C:
cd users
cd public
cd files

7. At this point your command prompt should look like c:\users\Public\Files>
8. Now type the following and hit enter:
xcopy /s Winsxs c:\windows\winsxs

9. If you did it correctly you will likely be prompted to overwrite a file. Hit Y on your keyboard. You will need to do this about 14 times.
10. Type exit in the command prompt and you will be back to the Choose an option screen.
11. Click the Continue button to reboot and get back in Windows.


Only do the next steps if everything above appeared to work successfully.


SFC Scan
1. Right-click on the Start button and select Command Prompt (Admin)
2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
 sfc /scannow

3. Once it finishes, copy and paste the following into the command-prompt window and press Enter.
copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

4. Once this has completed please go to your Desktop and you will find CBS.txt => Right-click on this file and choose Send To...Compressed (zipped folder). Please upload this zipped file CBS.zip to this thread

Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 

Attachments

This worked quite well, with one quirk.

Pasting the following command produced strange results.

Code: 
copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
copy : Cannot find path 'C:\WINDOWS\system32\%windir%\logs\cbs\cbs.log' because it does not exist.
At line:1 char:1
+ copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (C:\WINDOWS\syst...ogs\cbs\cbs.log:String) [Copy-Item], ItemNotFoundExce
   ption
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.CopyItemCommand

But I know my way around and got the file you needed. Here is the zip. Start menu now works, as does most other functions. Let me know if I should proceed to DISM.

View attachment CBS after repair.zip
 
Sorry about the issue you had but looks like you worked it out. OK, now that the SFC corruptions are fixed, let's do another check. Please do the following.

Step#1 - DISM /RestoreHealth Scan
Warning:this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Right-click on the Start button and select Command Prompt (Admin)
  2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
    Dism /Online /Cleanup-Image /RestoreHealth
  3. Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
    Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
OK, ran it. Did not get error 193 this time, but still did not get far.

Code: 
PS C:\WINDOWS\system32> dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.0

Image Version: 10.0.14393.0

[==========================100.0%==========================]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

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

This zip has both CPS and DISM logs.

View attachment CBS2.zip
 
OK, let's fix the following.
Code: 
(p) CSI Payload Corrupt   amd64_microsoft-windows-l..st-abovelockapphost_31bf3856ad364e35_10.0.14393.0_none_a1bf6fe9309a73e5\AboveLockAppHost.dll

Step#1 - SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please
 

Attachments

Here it is.

Code: 
SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-04-19 11:56:52.501
Microsoft Windows 10 Build 14393 - amd64
Using .zip script file at C:\Users\Luxamar\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\amd64_microsoft-windows-l..st-abovelockapphost_31bf3856ad364e35_10.0.14393.0_none_a1bf6fe9309a73e5

Successfully copied file C:\Users\Luxamar\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-l..st-abovelockapphost_31bf3856ad364e35_10.0.14393.0_none_a1bf6fe9309a73e5\AboveLockAppHost.dll to C:\WINDOWS\Winsxs\amd64_microsoft-windows-l..st-abovelockapphost_31bf3856ad364e35_10.0.14393.0_none_a1bf6fe9309a73e5\AboveLockAppHost.dll.

Successfully restored ownership for C:\WINDOWS\Winsxs\amd64_microsoft-windows-l..st-abovelockapphost_31bf3856ad364e35_10.0.14393.0_none_a1bf6fe9309a73e5
Successfully restored permissions on C:\WINDOWS\Winsxs\amd64_microsoft-windows-l..st-abovelockapphost_31bf3856ad364e35_10.0.14393.0_none_a1bf6fe9309a73e5
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2017-04-19 11:56:52.938
Script hash: bf5IugoQ+I8j5/jnMatD099WtYGZFx10oEda3Yrsa7c=
----------------------EOF-----------------------
 
Please do the following again.

Step#1 - DISM /RestoreHealth Scan
Warning:this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Right-click on the Start button and select Command Prompt (Admin)
  2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
    Dism /Online /Cleanup-Image /RestoreHealth
  3. Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
    Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
Here are the results. Looks like it may have worked.

Code: 
PS C:\WINDOWS\system32> dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.0

Image Version: 10.0.14393.0

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

View attachment CBS after DISM repair.zip
 
Thanks for your hard work in guiding me through this when every other source said I would have to reformat. My only remaining question is, where did you pull those files from that you sent me? As glad as I am to have this fixed, I am the kind of person who wants to know how a repair worked, mainly out of technical curiosity, but also to help others that have been affected by this issue.
 
That simple, eh? Thanks again. Go ahead and mark this solved.
For anyone else reading this, it looks like the Start Menu was fixed when we replaced my corrupted WinSxS files. Windows Update was fixed after DISM repair.
 
You must log in or register to reply here.

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

Back
Top