Page 9 of 15 FirstFirst ... 7891011 ... LastLast
  1.    21 Apr 2017 #81
    Join Date : Apr 2017
    Posts : 5
    Windows 10 1703

    Quote Originally Posted by fdegrove View Post
    It ignores the registry entries, that's why.


    Well how about that. Guess it makes sense since the hive isn't loaded. Seems like a glaring oversight in DISM to not warn of the fact it has limited abilities in that mode.
      My ComputerSystem Spec
  2.    22 Apr 2017 #82
    Join Date : Apr 2017
    Posts : 8,903
    windows 10 professional version 1607 build 14393.969 64 bit

    In the earlier post crystal diskinfo was recommended. I just downloaded it and it reported drive as good. That contradicts the UEFI diagnostics which indicate a failing drive. The crystal diskinfo is only using the smart test and can mislead users of the software as it only performs one test. The uefi diagnostics use short dst and long dst tests. This computer always passes the uefi smart test. It always fails the short dst test. The long dst can never run as the short one fails. Seatools for windows or the western digital drive tests may be as good as or better than the uefi diagnostics. I am looking for the best way to test internal hard drives as one of my drives has had recent chkdsk errors but all uefi studies have passed. I am wondering whether sanitizing the drive using the bios reduces the number of chkdsk errors (incorrect information in file record segments, attribute records corrupt, orphaned files).
      My ComputerSystem Spec
  3.    22 Apr 2017 #83
    Join Date : Apr 2017
    Posts : 2
    Windows 10 Creator's Update

    Quote Originally Posted by gommace View Post
    1. I followed the procedure explained by Eagle51 and found it successfull. After doing that, everything was perfect: CheckHealth, ScanHealth, Restore Health, sfc ... everything related with DISM. So, many thanks and congratulations to Eagle51!!!.
    2. Just to make a double-check, I imported back to the registry the two keys mentioned by him:


    • [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~0.0.0.0]

    • [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0]

    and previously exported to my Desktop, as Eagle51 explained ... and the DISM RestoreHealth error was again there.

    But, what I would like to know is if someone has found a definitive solution (without having to edit the registry) until MSFT decide to repair this problem in any way.
    There is one additional step you will have to perform in order to be successful: Move the file
    Code:
    C:\Windows\servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum
    out of that folder so DISM cannot find it.
    After that, no more errors.

    Kind regards,
    DAC324
      My ComputerSystem Spec
  4.    22 Apr 2017 #84
    Join Date : Jan 2015
    UK, Midlands
    Posts : 11,074
    Win 10 Pro (1703)

    Quote Originally Posted by zbook View Post
    In the earlier post crystal diskinfo was recommended. I just downloaded it and it reported drive as good. That contradicts the UEFI diagnostics which indicate a failing drive. The crystal diskinfo is only using the smart test and can mislead users of the software as it only performs one test. The uefi diagnostics use short dst and long dst tests. This computer always passes the uefi smart test. It always fails the short dst test. The long dst can never run as the short one fails. Seatools for windows or the western digital drive tests may be as good as or better than the uefi diagnostics. I am looking for the best way to test internal hard drives as one of my drives has had recent chkdsk errors but all uefi studies have passed. I am wondering whether sanitizing the drive using the bios reduces the number of chkdsk errors (incorrect information in file record segments, attribute records corrupt, orphaned files).
    Hard disk sentinel
    - tends to give good indications and more detailed
    Macrorit Diskscanner
    - free surface scanner
      My ComputerSystem Spec
  5.    22 Apr 2017 #85
    Join Date : Apr 2017
    Virtual Landmine
    Posts : 7
    Windows 10 Pro

    idk what happened but my system health report is back to normal now. weird.
      My ComputerSystem Spec
  6.    23 Apr 2017 #86
    Join Date : Jun 2016
    Posts : 10
    Windows 10 Pro x64

    Quote Originally Posted by DAC324 View Post
    There is one additional step you will have to perform in order to be successful: Move the file
    Code:
    C:\Windows\servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum
    out of that folder so DISM cannot find it. After that, no more errors.Kind regards,DAC324
    Although removing the registry keys and/or moving that location may work, it is still not a proper way to get rid of a system package as it can break the OS. You should not be technically moving/removing such packages, but uninstalling them. A good example is Cortana. Moving/deleting/renaming the Cortana package gets rid of SearchUI running in the background, but breaks Metro Start UI AND SFC /ScanNow can restore both - the deleted registry entries and the moved/deleted/renamed package folder.

    To properly get rid of a system package like that you should either use WIM_Tweak (very old and outdated, not recommended) or use another more modern method that always worked for me to get rid of all packages I did not want:
    - Search Google for NSudo 4.3 (or 4.0, both can be found through MDL forums), search for CBSEnum, and download both packages.
    - Run NSudo 4.3 (4.0 may also work) as Admin to launch CBSEnum with All Privelages as Trusted Installer.
    - Take ownership of the correct registry entry in CBSEnum (from the Edit button at the top of CBSEnum).
    - Use the Flat List to view packages, find the 2 Microsoft-Windows-TestRoot packages, and select/highlight both packages.
    - Right-click on highlighted packages, make both packages visible, de-couple both packages, and only then select to uninstall both packages (at once).
    - Restart, search for remaining package registry entries, remove the registry entries (which would not be the in same place, but in ToBeUninstalled or similar-named registry folder).
    - Restart again and you're done correctly uninstalling the package.
    - You can now proceed to safely run DISM RestoreHealth and SFC /ScanNow without fear or having those packages restored and those error re-appearing.
      My ComputerSystem Spec
  7.    23 Apr 2017 #87
    Join Date : Jun 2015
    Posts : 540
    Windows 10 Pro 64bit; Windows 10 TP; KDE Neon

    Quote Originally Posted by MonarchX View Post
    Although removing the registry keys and/or moving that location may work, it is still not a proper way to get rid of a system package as it can break the OS. You should not be technically moving/removing such packages, but uninstalling them. A good example is Cortana. Moving/deleting/renaming the Cortana package gets rid of SearchUI running in the background, but breaks Metro Start UI AND SFC /ScanNow can restore both - the deleted registry entries and the moved/deleted/renamed package folder.

    To properly get rid of a system package like that you should either use WIM_Tweak (very old and outdated, not recommended) or use another more modern method that always worked for me to get rid of all packages I did not want:
    - Search Google for NSudo 4.3 (or 4.0, both can be found through MDL forums), search for CBSEnum, and download both packages.
    - Run NSudo 4.3 (4.0 may also work) as Admin to launch CBSEnum with All Privelages as Trusted Installer.
    - Take ownership of the correct registry entry in CBSEnum (from the Edit button at the top of CBSEnum).
    - Use the Flat List to view packages, find the 2 Microsoft-Windows-TestRoot packages, and select/highlight both packages.
    - Right-click on highlighted packages, make both packages visible, de-couple both packages, and only then select to uninstall both packages (at once).
    - Restart, search for remaining package registry entries, remove the registry entries (which would not be the in same place, but in ToBeUninstalled or similar-named registry folder).
    - Restart again and you're done correctly uninstalling the package.
    - You can now proceed to safely run DISM RestoreHealth and SFC /ScanNow without fear or having those packages restored and those error re-appearing.


    Hi,

    I have no reason to doubt your suggestion, especially since I have not tested it myself, but I have just run SFC /SCANNOW and the Registry keys I have deleted have not been restored in my Registry. See posts : 39, 40 and 41 of this thread, please. I have not run DISM again, after that time, but running SFC a few minutes ago has not restored those 2 keys back. Finally, since deleting them I have not faced any issue with my OS. I agree that those should be left in peace (undeleted), though.

    EDIT:
    I have just run DISM, as well. Those two Reg keys I have deleted (see post 39) have not been restored.

    Click image for larger version. 

Name:	r.png 
Views:	7 
Size:	121.6 KB 
ID:	131673


    I tend to agree though that this is not an appropriate fix.
    Last edited by Joanne; 23 Apr 2017 at 14:25.
      My ComputerSystem Spec
  8.    24 Apr 2017 #88
    Join Date : Aug 2015
    Posts : 15
    Windows 10

    Me too ... but my big concern is what would happen if I needed to repair the system.
      My ComputerSystem Spec
  9.    24 Apr 2017 #89

    Guys like people have said before just wait for Microsoft to fix this issue as well as the other issues they have given us. I have learned that when you try to fix it on your own it just causes more issues down the road.
      My ComputerSystem Spec
  10.    24 Apr 2017 #90
    Join Date : Aug 2016
    S/E England
    Posts : 4,526
    10 Home x64 (1709) (10 Pro on 2nd pc)

    Quote Originally Posted by gommace View Post
    ... but my big concern is what would happen if I needed to repair the system.
    Boot from the install media or boot to Advanced Startup. Get the Command prompt and do an offline repair.
    Code:
    DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:ESD:D:\x64\sources\install.esd:2 /ScratchDir:C:\Scratch
    (We have DonCuthbert to thank for this)
    Use DISM to Repair Windows 10 Image

    On my 15063.138 system using DISM offline completes successfully.

    Notes:
    • use ...esd:1 for Pro, ...esd:2 for Home.
    • you have to create the 'C:\Scratch' folder yourself before you try this command.
      My ComputersSystem Spec

 
Page 9 of 15 FirstFirst ... 7891011 ... 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 12:07.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums