Page 2 of 15 FirstFirst 123412 ... LastLast
  1.    11 Apr 2017 #11

    More interesting data: reading up on using DISM I learned that it sometimes has more difficulty with esd files than with wim files. The install file in the Media Creation Tool version of 1703 is install.esd. So I hied me off to MSDN and downloaded the latest and greatest ISO file from there and found exactly the same repair issue from that supposedly more usable, DISM friendly version:
    Click image for larger version. 

Name:	post-1704-dism-fail.jpg 
Views:	7 
Size:	133.5 KB 
ID:	129472
    I'll be blogging about this tomorrow, but it seems pretty clear that whatever is causing the issue with component store corruption is (a) coming from Microsoft and (b) not currently fixable through ordinary DISM measures. I've now tried both the ESD file from the media I used to upgrade my OS and the WIM file from the MSDN ISO, both with the same failure.
    Very interesting!
    --Ed--
      My ComputersSystem Spec
  2.    11 Apr 2017 #12
    Join Date : Dec 2015
    Posts : 28
    Windows 10 Pro x64
    Thread Starter

    Quote Originally Posted by EdTittel View Post
    More interesting data: reading up on using DISM I learned that it sometimes has more difficulty with esd files than with wim files. The install file in the Media Creation Tool version of 1703 is install.esd. So I hied me off to MSDN and downloaded the latest and greatest ISO file from there and found exactly the same repair issue from that supposedly more usable, DISM friendly version:
    Click image for larger version. 

Name:	post-1704-dism-fail.jpg 
Views:	7 
Size:	133.5 KB 
ID:	129472
    I'll be blogging about this tomorrow, but it seems pretty clear that whatever is causing the issue with component store corruption is (a) coming from Microsoft and (b) not currently fixable through ordinary DISM measures. I've now tried both the ESD file from the media I used to upgrade my OS and the WIM file from the MSDN ISO, both with the same failure.
    Very interesting!
    --Ed--
    Yeah. Could you also check administrative event viewer errors If it is not a problem? I keep getting them on every install

      My ComputerSystem Spec
  3.    11 Apr 2017 #13

    I just checked my Windows logs looking for Critical, Error, and Warning items and I have very little (almost no) overlap with what I see showing in your post. No DCOM items following the upgrade to Creators Update, in fact.
    HTH,
    --Ed--
      My ComputersSystem Spec
  4.    11 Apr 2017 #14
    Join Date : Aug 2016
    S/E England
    Posts : 4,477
    10 Home x64 (1709) (10 Pro on 2nd pc)

    No change after today's Cumulative Update KB4015583 Windows 10 v1703 Build 15063.138

    Code:
    C:\WINDOWS\system32> DISM /Online /Cleanup-Image /RestoreHealth
    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0
    Image Version: 10.0.15063.0
    [===========================98.7%========================= ]
    Error: 0x800f081f
    The source files could not be found.
      My ComputersSystem Spec
  5.    11 Apr 2017 #15

    Thanks, Bree: good to know. This could be a while, then...
    --Ed--
      My ComputersSystem Spec
  6.    11 Apr 2017 #16

    Thanks, Bree: good to know. This could be a while, then...
    --Ed--
      My ComputersSystem Spec
  7.    12 Apr 2017 #17
    Join Date : Apr 2017
    Posts : 14
    whiggs

    Hey guys. I also have this issue as well. I have installed numerous windows 10 creator update os installations (4 total) and every single one has exhibited the exact same issue. It was a major pain that ate up 2 days (because Microsoft scheduling is just crap like that and every customer support rep has to walk you through troubleshooting steps you have already tried so they can figure out for themselves that it is not an issue that they can fix), but I was able to actually speak to a level 2 tech at Microsoft who (after also going through the exact same troubleshooting steps myself and every other tech before her had already tried, while I am ripping my hair out), gathered the dism logs concerning the issue to send off to the software engineers. It shocks me just how incompetent a level 2 engineer from Microsoft can be concerning not a single one of the technicians or level 2 ever actually looked at the DISM log files for information as to the cause of the issue and I was forced to verbally re communicate the contents of the log files, since they were unable to read. But I digress, what I find most interesting is, if you download Tweaking.com's Windows all in one repair tool (Tweaking.com - Windows Repair Free/Pro), and perform a pre-scan of the operating system (which entails scanning for missing or corrupt packaging files, scanning the environment variables, and the reparse points for the operating system), in every single operating system that the Creators update Version of Windows 10, the following result is returned by the scan:These Files Are Possibly Corrupt (Bad Digital Signature): (Total: 1)C:\Windows\servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum¦ 1 Combined Problems were found with the packages files, these files need to be replaced (These mainly only effect installing Windows Updates.)¦ The SFC (System File Checker) doesn't scan and replace some of these files, so you may need to replace them manually.Interesting right? The aspect that I find even MORE interesting is that even when I extracted the exact same file from the Creators update installation iso "install.wim" and replace the supposed corrupt file with the brand new one, when I re-run the scan, no change at all. This may explain the cause of DISM failing, considering that DISM (if no source is specified) downloads the files it needs from Windows update. Also, looking at the log file (I deleted the old log file and ran the scan so that I would have only the errors associated with a single run), the following are the warnings and errors that were reported:2017-04-11 12:36:01, Warning DISM DISM OS Provider: PID=23072 TID=24252 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::Final_OnConnect2017-04-11 12:36:01, Warning DISM DISM Provider Store: PID=23072 TID=24252 Failed to Load the provider: C:\Users\whiggs\AppData\Local\Temp\BB4A7318-151D-4606-9F4A-81DB7ED04B5D\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2017-04-11 12:36:01, Warning DISM DISM Provider Store: PID=23072 TID=24252 Failed to Load the provider: C:\Users\whiggs\AppData\Local\Temp\BB4A7318-151D-4606-9F4A-81DB7ED04B5D\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2017-04-11 12:42:37, Info DISM DISM Package Manager: PID=23072 TID=25464 Error in operation: source for package or file not found, ResolveSource() unsuccessful. (CBS HRESULT=0x800f081f) - CCbsConUIHandler::Error

    2017-04-11 12:42:37, Error DISM DISM Package Manager: PID=23072 TID=24252 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)

    2017-04-11 12:42:37, Error DISM DISM Package Manager: PID=23072 TID=24252 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)

    2017-04-11 12:42:37, Error DISM DISM Package Manager: PID=23072 TID=24252 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg

    2017-04-11 12:42:37, Error DISM DISM Package Manager: PID=23072 TID=24252 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800f081f)

    2017-04-11 12:42:37, Error DISM DISM Package Manager: PID=23072 TID=24252 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)

    Now I don't know what a provider is, but I find it odd that DISM is looking for it in the temporary directory of the current user. I also find it odd how it is unable to recognize C:\windows as a folder. Any thoughts?
      My ComputerSystem Spec
  8.    12 Apr 2017 #18

    I blogged about this further this morning (Creators Update Image Integrity Gotcha - Windows Enterprise Desktop). The only machines I have that manifest this problem have Nvidia graphics cards, and the error centers around the inability to find the Nvidia sound driver (NVIDIA High Definition Audio). This is highly reminiscent of last year's troubles with elements of the Nvidia graphics driver environment. Hopefully, MS and Nvidia will be able to synch up for the next cumulative update and get this fixed.
    --Ed--

    PS: I'm not sure this has any bearing on the preceding post. In particular the error message about C:\Windows is entirely different from what I'm seeing, and FWIW, I agree that this oversight or omission is cause for consternation if not concern. It also diagnoses like a Microsoft problem, however, just like the error I ran to ground on my local machines.
    Last edited by EdTittel; 12 Apr 2017 at 14:39. Reason: Respond to previous post
      My ComputersSystem Spec
  9.    12 Apr 2017 #19
    Join Date : Apr 2017
    Posts : 2
    Windows 10 1703

    My Surface Pro 3 is exhibiting this same behavior. Reinstalling Edge through the delete and powershell does not fix the issue. I do not have an NVidia card, just integrated graphics.

    When I open Edge, it shows a blank white page and force quits eventually (or I kill it in task manager). Tried off the domain, new user, deleting edge folder in safe mode. Nothing seems to work. SFC comes out clean, DISM is exhibiting the same behavior trying to repair from ESD file (ISO and Media Creation Tool USB).
      My ComputerSystem Spec
  10.    12 Apr 2017 #20
    Join Date : Dec 2015
    Posts : 28
    Windows 10 Pro x64
    Thread Starter

    All in all, it has been really buggy update for me.

    Dism is broken.

    Games ignore nvidia color profiles.

    Also, I have worse performance overall on benchmarks with random microstutters.. Made multiple clean installs. My only guess is that drivers are still not compatible with Creators update.

    Lots of event viewer errors.
      My ComputerSystem Spec

 
Page 2 of 15 FirstFirst 123412 ... LastLast


Similar Threads
Thread Forum
Windows 10 Creators Update and Creators Update SDK are Released
Source: Windows 10 Creators Update and Creators Update SDK are Released - Building Apps for WindowsBuilding Apps for Windows :arrow: Windows 10 Creators Update version 1703 (build 15063) now available from Windows 10 Update Assistant. ...
Windows 10 News
STORE cache corruption
Store apps work fine yet STORE apps troubleshooter reports that "Windows STORE cache may be damaged/corrupted." Despite the following measures the error is "not fixed." STORE has been reset (WSRESET). STORE apps have been reregistered....
Software and Apps
KB3194496 - Corrupts Component Store?
Hi. I've been trying to install update KB3194496, but without success. Before installing it, DISM /CheckHealth reports "No component store corruption detected.". When trying to install the update, DISM aborts giving the error code 0x80073712...
Windows Updates and Activation
bios post screen shows incoherent component info
i boot up the computer and the bios post screen shows normal except for 4 keyboards 2 mice 2 hubs. when i only have 1 keyboard and 1 mice connected. what is this all about? idk what hubs is. maybe the dvd rom drive?
Drivers and Hardware
Solved DISM failure cannot repair corruption, error 0x80070570
I am unable to repair some filesystem corruption after upgrading from Windows 7 to Windows 10. Both sfc and DISM fail to fix the issues. I've attached the CBS.log and dism.log files if anyone would be willing to help me figure this out, thanks! ...
Performance & Maintenance
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 22:07.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums