Windows 10: Win 10 1703; How to fix broken DISM and hence Windows Update? Solved

Page 1 of 3 123 LastLast
  1.    4 Weeks Ago #1

    Win 10 1703; How to fix broken DISM and hence Windows Update?


    Hello. My Win 10 Win Update auto upgraded to 1703 some time ago, but it stalls for 1703 => 1709, returning error 0x800700C1. SFC /scannow found errors but could not fix, so I went to DISM. But it fails too. Typical errors:

    Code:
    018-01-18 03:13:46, Warning               DISM   DISM Provider Store: PID=1352 TID=4424 There is a possible 32-bit versus 64-bit cross architecture issue with the provider (or one of its dependencies). - CDISMProviderStore::Internal_LoadProvider(hr:0x800700c1)
    2018-01-18 03:13:46, Warning               DISM   DISM Provider Store: PID=1352 TID=4424 Failed to Load the provider: C:\Windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x800700c1)
    2018-01-18 03:13:46, Info                  DISM   DISM Provider Store: PID=1352 TID=4424 Connecting to the provider located at C:\Windows\System32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2018-01-18 03:13:46, Info                  DISM   DISM Provider Store: PID=1352 TID=4424 Connecting to the provider located at C:\Windows\System32\Dism\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2018-01-18 03:13:46, Info                  DISM   DISM Provider Store: PID=1352 TID=4424 Connecting to the provider located at C:\Windows\System32\Dism\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2018-01-18 03:13:46, Info                  DISM   DISM Provider Store: PID=1352 TID=4424 Connecting to the provider located at C:\Windows\System32\Dism\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2018-01-18 03:13:46, Info                  DISM   DISM Provider Store: PID=1352 TID=4424 Connecting to the provider located at C:\Windows\System32\Dism\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2018-01-18 03:13:46, Warning               DISM   DISM Provider Store: PID=1352 TID=4424 Failed to Load the provider: C:\Windows\System32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2018-01-18 03:13:46, Warning               DISM   DISM Provider Store: PID=1352 TID=4424 Failed to Load the provider: C:\Windows\System32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    [1352] [0x8007007b] FIOReadFileIntoBuffer:(1259): The filename, directory name, or volume label syntax is incorrect.
    [1352] [0xc142011c] UnmarshallImageHandleFromDirectory:(639)
    [1352] [0xc142011c] WIMGetMountedImageHandle:(2893)
    2018-01-18 03:13:46, Info                  DISM   DISM WIM Provider: PID=1352 TID=4424 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
    2018-01-18 03:13:46, Info                  DISM   DISM VHD Provider: PID=1352 TID=4424 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
    2018-01-18 03:13:46, Info                  DISM   DISM VHD Provider: PID=1352 TID=4424 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
    2018-01-18 03:13:46, Info                  DISM   DISM Imaging Provider: PID=1352 TID=4424 The provider VHDManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
    [1352] [0x8007007b] FIOReadFileIntoBuffer:(1259): The filename, directory name, or volume label syntax is incorrect.
    [1352] [0xc142011c] UnmarshallImageHandleFromDirectory:(639)
    [1352] [0xc142011c] WIMGetMountedImageHandle:(2893)
    2018-01-18 03:13:46, Info                  DISM   DISM WIM Provider: PID=1352 TID=4424 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
    2018-01-18 03:13:46, Info                  DISM   DISM Imaging Provider: PID=1352 TID=4424 The provider WimManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
    2018-01-18 03:13:46, Info                  DISM   DISM Imaging Provider: PID=1352 TID=4424 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage
    2018-01-18 03:13:46, Error                 DISM   API: PID=1352 TID=4424 onecore\base\ntsetup\opktools\dism\api\lib\imagingcommandobject.cpp:499 - CAttachPathCommandObject::InternalExecute(hr:0x80070032)
    2018-01-18 03:13:46, Error                 DISM   API: PID=1352 TID=4424 InternalExecute failed - CBaseCommandObject::Execute(hr:0x80070032)
    2018-01-18 03:13:46, Error                 DISM   API: PID=1352 TID=5412 CAttachPathCommandObject failed - DismOpenSessionInternal(hr:0x80070032)
    In case anyone knows how to read this LOL. Note that the 0x800700C1 error (which I find absent from MS error compendia) is in the first couple lines, which is why I'm guessing the failure of WinUpdate to do the upgrade is related to this. (WU does deliver the incidental patches to 1703.)

    So I figure I need to repair DISM, but from my reading, it needs to be an "offline repair". Does the following plan seem correct.
    1. Download an iso of Win 10 Pro 1703.
    2. Mount it to virtual drive "X".
    3. Boot from a burn of the downloaded iso.
    3. Run "Dism /Image:C:\offline /Cleanup-Image /RestoreHealth /Source:X:\test\mount\windows"
    where C is my normal boot drive. (I copied that and need to check the syntax.)

    Questions: Does that approach seem correct? Does the offline switch mean indeed that you've booted from an external disc you've created from the fresh iso.

    Am I right that I should NOT run

    "Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:X:\sources\install.esd:1 /limitaccess" (or the equivalent where the source reference is to "install.wim"), because that would be like asking a broken system to repair itself? (I did try it once and it failed.)

    How do you ensure that when you download - or use the Creation Tool to get - a Win 10 pro iso, you get only the 1703 version? That's what my source should be, right? Or does it not matter?

    As you see, I'm a little confused. Ok, a lot confused. Would appreciate pointers or advice.

    Many thanks. -Ron
      My ComputerSystem Spec

  2.    4 Weeks Ago #2

    Hi Ron,
    I just ran into this issue a few days ago and made some notes:

    Windows 10 Recovery Tools - Bootable Rescue Disk

    Remember if you are booting PE you are probably wanting to do things to the Windows image mounted at C (to which you'll have full unrestricted access if it is mounted), not the PE environment that you are running.


    For example you don't want to use DISM to repair the PE image. You want to be repairing the offline Windows image so rather than specifying /online you'd specify the image you want to repair. Like this



    dism /image:c:\ /cleanup-image /restorehealth /source:wim:X:\sources\install.wim:1
    Windows 10 Recovery Tools - Bootable Rescue Disk

    I don't know how to do a validation of the wim file in a offline instalation...

    this line is use to do the validation using SFC


    sfc /scannow /offbootdir=L:\ /offwindir=L:\Windows\
    Windows 10 Recovery Tools - Bootable Rescue Disk

    If your image is D:\sources\install.wim then mount it using the following command from within PE:
    "DISM.exe /mount-Image /ImageFile:d:\sources\install.wim /index:1 /mountdir:C:\mount"
    Then:
    "DISM.exe /Image:WindowsDriveletterhere:\ /Cleanup-image /Restorehealth /Source:c:\mount\windows /LimitAccess"
    To get your hands on a CU v1703, you could use the Windows ISO Downloader from Heidoc.net

    Microsoft Windows and Office ISO Download Tool

    It downloads directly from Microsoft.

    However, you might just be better off doing something called an in-place repair, or in-place upgrade: Download the latest ISO (FCU v1709), mount the ISO, and run setup.exe. That will upgrade you to the Fall Creators Update v1709 and keep all your files and programs.

    Here's the tut:

    Repair Install Windows 10 with an In-place Upgrade Installation Upgrade Tutorials

    .
      My ComputerSystem Spec

  3.    4 Weeks Ago #3

    Thank you simric for the extensive notes and refs. Didn't know about that iso downloader. Very handy.

    I decided to try the repair in place, using the 1703 iso (same version I'm at now). The setup went fine with all the preliminary stuff, and I specified keep files & apps, but unfortunately, it failed at about 20% of the actual installation.

    The DISM log shows activity during most of the time the operation was executing, so it appears a fresh iso install-repair in place will not fix it. The following code shows chunks of the errors from the DISM log. The final chunk shown repeated over and over. With respect to the second chunk, the file SiloedPackageProvider.dll is in my DISM folder, but the second two dll's are not.
    Code:
    .
    .
    .
    2018-01-20 15:15:24, Warning               DISM   DISM Provider Store: PID=6832 TID=8608 There is a possible 32-bit versus 64-bit cross architecture issue with the provider (or one of its dependencies). - CDISMProviderStore::Internal_LoadProvider(hr:0x800700c1)
    2018-01-20 15:15:24, Warning               DISM   DISM Provider Store: PID=6832 TID=8608 Failed to Load the provider: C:\Windows\system32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x800700c1)
    .
    .
    2018-01-20 15:15:24, Warning               DISM   DISM Provider Store: PID=6832 TID=8608 Failed to Load the provider: C:\Windows\system32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2018-01-20 15:15:24, Warning               DISM   DISM Provider Store: PID=6832 TID=8608 Failed to Load the provider: C:\Windows\system32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    [6832] [0x8007007b] FIOReadFileIntoBuffer:(1259): The filename, directory name, or volume label syntax is incorrect.
    [6832] [0xc142011c] UnmarshallImageHandleFromDirectory:(639)
    [6832] [0xc142011c] WIMGetMountedImageHandle:(2893)
    .
    .
    2018-01-20 16:31:49, Warning               DISM   DISM OS Provider: PID=10816 TID=6964 Failed to bind the online servicing stack - CDISMOSServiceManager::get_ServicingStackDirectory(hr:0x800700c1)
    2018-01-20 16:31:49, Error                 DISM   DISM OS Provider: PID=10816 TID=6964 "Unable to retrieve servicing stack folder for DLL search path modification." - CDISMOSServiceManager::SetDllSearchPath(hr:0x800700c1)
    2018-01-20 16:31:49, Warning               DISM   DISM OS Provider: PID=10816 TID=6964 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::Final_OnConnect
    .
    .
    2018-01-20 16:33:46, Error                 DISM   DISM OS Provider: PID=6972 TID=92 "Unable to retrieve servicing stack folder for DLL search path modification." - CDISMOSServiceManager::SetDllSearchPath(hr:0x800700c1)
    2018-01-20 16:33:46, Error                 DISM   DISM OS Provider: PID=6972 TID=92 Failed trying to determine the OS Version. HRESULT=0x800700c1 - CDISMOSServiceManager::get_OSVersion
    2018-01-20 16:33:46, Error                 DISM   API: PID=7812 TID=7468 onecore\base\ntsetup\opktools\dism\api\lib\dismcore.cpp:523 - CDismCore::LogImageSessionDetails(hr:0x800700c1)
    2018-01-20 16:33:46, Error                 DISM   API: PID=7812 TID=7468 Failed to log image session details. HRESULT=800700C1 - CDismCore::CheckAndConfigureOSServices(hr:0x800700c1)
    2018-01-20 16:33:46, Error                 DISM   API: PID=7812 TID=7468 Could not check and configure OS Services - CDismCore::CacheImageSession(hr:0x800700c1)
    2018-01-20 16:33:46, Error                 DISM   API: PID=7812 TID=7468 InternalExecute failed - CBaseCommandObject::Execute(hr:0x800700c1)
    2018-01-20 16:33:46, Error                 DISM   API: PID=7812 TID=8732 CAttachPathCommandObject failed - DismOpenSessionInternal(hr:0x800700c1)
    [7812] [0x8007007b] FIOReadFileIntoBuffer:(1259): The filename, directory name, or volume label syntax is incorrect.
    [7812] [0xc142011c] UnmarshallImageHandleFromDirectory:(639)
    [7812] [0xc142011c] WIMGetMountedImageHandle:(2893)
    [7812] [0x8007007b] FIOReadFileIntoBuffer:(1259): The filename, directory name, or volume label syntax is incorrect.
    [7812] [0xc142011c] UnmarshallImageHandleFromDirectory:(639)
    [7812] [0xc142011c] WIMGetMountedImageHandle:(2893)
    .
    .
    I suspect the problem could be interpreted from these error messages. I don't know how to do that.

    I guess I'll have to summon the nerve to do an offline DISM repair of my OS. I now have various folders in my root directory related to prior update attempts. (eg. $WINDOWS.~BT etc.) Would appreciate advice on what can be safely removed for fear of interfering with a repair attempt.

    I think I read somewhere that this problem may have been caused by a prior update process where WU made some incorrect changes to the registry, and that the reason an offline repair is more likely to succeed is that it doesn't refer to the registry. Not sure about that. There are various reports of people having problems with the 1607=>1703 upgrade due to a MS error, but it was supposed to have been fixed with a patch around May, 2017. Since my 1703 has been patching successfully (but not upgrading), I assume I don't have whatever that problem was.

    Anyway, thanks again. -Ron
      My ComputerSystem Spec

  4.    4 Weeks Ago #4

    Hi Ron.
    I have to admit, I'm not very good looking at DISM logs. I do agree with you that it appears an offline repair may be the way to go. All those links I posted were from a thread here, which has a custom rescue environment put together by one of our members, Kyhi (on the first page of the thread). It's the best for working on a system "offline".

    I would have done the repair install using the latest and greatest ISO. I've done several in-place repairs on others' and my systems, and always used the latest ISO. Never had a failure yet, but then, not sure exactly what is going on with your system. Some AVs will prevent a proper upgrade; some NICs as well. I will mention, if you've got any 3rd-party anti-virus or anti-malware, or MB monitoring software, disable or uninstall all of it before trying again. Run CHKDSK on the OS drive. Disconnect all peripherals except keyboard, mouse and monitor. If you've moved your user files to another drive, move the pointers back. Make sure all software is up-to-date; drivers, chipset and BIOS are current, etc. If you've got a separate GPU inside, you could try disconnecting that and just use the integrated graphics for the repair process.

    Perhaps others will chime in and have more info for you about your logs.
      My ComputerSystem Spec


  5. Posts : 391
    Windows 10 Home x64
       4 Weeks Ago #5

    I'm certainly no expert on DISM, the first thing that popped out was on the first line of the log. Apparently there's some discrepancy with x32 versus x64 architecture. Your system shows x64.

    There is a possible 32-bit versus 64-bit cross architecture issue with the provider (or one of its dependencies). - CDISMProviderStore::Internal_LoadProvider
    I don't know enough about DISM logs to know if that's an issue, maybe it's nothing, but it looks like it could be a potential problem.

    Good luck
      My ComputersSystem Spec


  6. Posts : 14,238
    windows 10 professional version 1607 build 14393.969 64 bit
       4 Weeks Ago #6
      My ComputerSystem Spec

  7.    4 Weeks Ago #7

    Thanks to you all for suggestions. Will respond as I learn more.
    @zbook Yes, thanks, I had intended to try that. I'm not familiar with PS (or DISM for that matter), so wanted to proceed cautiously. In PowerShell, I tried:

    PS C:\Windows\system32> repair-windowsimage -online -checkhealth
    repair-windowsimage : The request is not supported.
    At line:1 char:1
    + repair-windowsimage -online -checkhealth
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: ( [Repair-WindowsImage], COMException
    + FullyQualifiedErrorId : Microsoft.Dism.Commands.RepairWindowsImageCommand
    What's up with that? If I understand correctly, the comandlet I issued is a PS version of DISM. Does the error mean my DISM is completely broken? -Ron
      My ComputerSystem Spec


  8. Posts : 14,238
    windows 10 professional version 1607 build 14393.969 64 bit
       4 Weeks Ago #8

    Run this log collector and post a zip into this thread for troubleshooting:
    log collector v2-beta08.zip

    Create a bootable windows 10 iso from the Microsoft website:
    Download Windows 10
    It will be in the esd format.
    Insert the flash drive into any USB port.
    Open file explorer and identify the drive letter for the bootable windows 10 iso.

    Open administrative command prompt and type or copy and paste:
    1) sfc /scannow
    2) dism /online /cleanup-image /scanhealth
    3) dism /online /cleanup-image /restorehealth
    4) chkdsk /scan
    5) dism /online /cleanup-image /RestoreHealth /limitaccess
    6) Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:E:\Sources\Install.esd:1 /limitaccess
    (Change the letter E to the drive letter that you saw in file explorer for the bootable windows 10 iso flash drive)
    7) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
      My ComputerSystem Spec

  9.    4 Weeks Ago #9

    Per request. Note: logs were collected before the scans. Thanks for the assistance!
    ****************
    EDIT: BTW, I would like to call your attention to this thread:
    DISM error 193 - Microsoft Community
    I will compare my C:\Windows\System32\Downlevel directory to the one on my laptop which did successfully upgrade (automatically) to 1709.

    EDIT2: Ok, I notice my 1709 laptop has 96 items in folder Downlevel, compared to 95 in my 1703 desktop. The additional file in 1709 appears to be: api-ms-win-shcore-stream-I1-1-0.dll Should I try putting a copy of it in the Downlevel folder of the 1703? Note: I have not meticulously compared the two directories file by file.
    *******************
    Microsoft Windows [Version 10.0.15063]
    (c) 2017 Microsoft Corporation. All rights reserved.

    C:\Windows\system32>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection found corrupt files but was unable to fix some
    of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
    example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
    supported in offline servicing scenarios.

    C:\Windows\system32>dism /online /cleanup-image /scanhealth

    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0


    Error: 193

    An error occurred accessing the DISM binaries on the host system.
    Ensure that the local DISM binaries exist and that you have Read permission on the folder.

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

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

    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0


    Error: 193

    An error occurred accessing the DISM binaries on the host system.
    Ensure that the local DISM binaries exist and that you have Read permission on the folder.

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

    C:\Windows\system32> chkdsk /scan
    The type of the file system is NTFS.

    Stage 1: Examining basic file system structure ...
    932608 file records processed.
    File verification completed.
    15475 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    1102562 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    84978 data files processed.
    CHKDSK is verifying Usn Journal...
    38312960 USN bytes processed.
    Usn Journal verification completed.

    Windows has scanned the file system and found no problems.
    No further action is required.

    1953000447 KB total disk space.
    786182940 KB in 621842 files.
    375504 KB in 84979 indexes.
    0 KB in bad sectors.
    1105855 KB in use by the system.
    65536 KB occupied by the log file.
    1165336148 KB available on disk.

    4096 bytes in each allocation unit.
    488250111 total allocation units on disk.
    291334037 allocation units available on disk.

    C:\Windows\system32>dism /online /cleanup-image /RestoreHealth /limitaccess

    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0


    Error: 193

    An error occurred accessing the DISM binaries on the host system.
    Ensure that the local DISM binaries exist and that you have Read permission on the folder.

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

    C:\Windows\system32>Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:P:\Sources\Install.esd:1 /limitaccess

    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0


    Error: 193

    An error occurred accessing the DISM binaries on the host system.
    Ensure that the local DISM binaries exist and that you have Read permission on the folder.

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

    C:\Windows\system32>
    Win 10 1703; How to fix broken DISM and hence Windows Update? Attached Files
    Last edited by rkl122; 4 Weeks Ago at 16:52.
      My ComputerSystem Spec


  10. Posts : 14,238
    windows 10 professional version 1607 build 14393.969 64 bit
       4 Weeks Ago #10

    The computer windows version and build are: 10.0, Build 15063
    The failure error was: 0x800700C1
    This code:
    0x000000C1ERROR_BAD_EXE_FORMAT%1 is not a valid Win32 application.
    There was a problem reported running an application: Bad Image : Exception Processing Message 0xc000007b


    There are Acronis and Macrium backup images.
    The BIOS is legacy.

    1) In the left lower corner search type system > open system control panel > on the left pane click advanced system settings > under performance click settings > on the performance options window click the advanced tab > under virtual memory click change > post an image of the virtual memory window into the thread.

    2) In the left lower corner search type system > open system control panel > on the left pane click advanced system settings > under startup and recovery click settings > post an image of the startup and recovery windows into the thread.

    3) Open Ccleaner > click on the windows tab > scroll down to system and advanced > post an image into the thread

    4) Please confirm that there is an Acronis backup image
    5) Please confirm that there is an Macrium backup image
    6) Consider performing a clean install of Windows 1709 and restoring the image.
    7) Consider an in place upgrade repair
    8) Open disk management > widen the status and volume columns > post an image into the thread
    Disk Management - How to Post a Screenshot of General Tips Tutorials
    9) Download and install Minitool partition wizard > post an image into the thread:
    MiniTool Partition Wizard Free Edition - Free download and software reviews - CNET Download.com


    Code:
    Event[1321]:  Log Name: System  Source: Application Popup  Date: 2018-01-07T22:00:26.462  Event ID: 26  Task: N/A  Level: Information  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-2AD3U8J  Description: Application popup: Windows - Bad Image : Exception Processing Message 0xc000007b Parameters 0x7ff860b017a8 0xffffffffc0000428 0x7ff860b017a8 0x7ff860b017a8
    Code:
    Event[2165]:  Log Name: System  Source: Microsoft-Windows-WindowsUpdateClient  Date: 2018-01-15T17:02:42.639  Event ID: 20  Task: Windows Update Agent  Level: Error  Opcode: Installation  Keyword: Installation,Failure  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-2AD3U8J  Description: Installation Failure: Windows failed to install the following update with error 0x800700C1: Feature update to Windows 10, version 1709.
      My ComputerSystem Spec


 
Page 1 of 3 123 LastLast

Related Threads
Solved Windows 10 update 1703 in Windows Updates and Activation
I found this update this morning. It has been "installing" now for 3 hours and sees to be in a loop where it shows Dowloading Updates, Preparing to install updates, then goes back to Downloading Updates. Is this a loop or wilI it complete?
In case anyone needs the restorehealth command to fix their operating system it is now working for version 1703: Windows PowerShell Copyright (C) 2016 Microsoft Corporation. All rights reserved. PS C:\Windows\system32> sfc /scannow ...
Hi , two days ago ( 2/5/2017) upgraded my windows 10 system from ver.1607 to ver.1703 , so called Creators update and immediately ran sfc /scannow ( no integrity violation ), DISM /Online /Cleanup-Image /ScanHealth ( component store repairable )...
Could someone running this CU Pro version please run the report to see if they get the same failing results?: 128599 I did not find any issues when running the CU Home version on another rig: 128600
Really strange. Unsure what is going on here. I upgraded to 14251 last week. DISM was broken from the get go so I went back to prior version...then 14257 came out this week. Just installed it today. Same thing. On first bootup dism/restorehealth...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 04:10.
Find Us