Any way to make this generic? For all who use you must edit the package name to reflect your build of Windows. For example in remove.ps1, you would need to change 15063.0 to 16184.1001 if you are using latest IP!
MonarchX: Remove-WindowsPackage remove manual ownership registry. = no problem = Code: Takeown-Registry ("HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\$pkg") Takeown-Registry ("HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\$pkg\Owners") no exist registry after uninstalled the package.
That is IF it gets removed. I mentioned that the second part of the guide (using PS scripts, merging registry entries, and taking ownership) did not work for me - packages remained and I could not restore ownership to them because taking ownership worked, but restoring ownership was denied. I am not saying it is the wrong way to do things - I am sure there are 10+ ways of achieving the same result. I simply look at my mistakes as a semi-newbie tweaked and want to help others not make the same mistake. People are not that different from each other - if I messed up by taking ownership with a simple .reg tweak that provided the expected result, but bit me in the butt later, then there are others who had the same thing happen, but they aren't likely to post that. I am going to post a reply in that thread on how you can further help yourself with de-bloating the OS without removing packages, but by uninstalling and de-activating them without removal, which in turn, will make their removal (if desired after uninstallation and de-activation) easier with any method. I ALSO got most of that info from MDL, but changed something to make it easier. Unforuntely, such excellent posts and guides are not always original posts, but someone's replies that do not get noticed and fade away without becoming stickies.
much faster method here and almost anybody can do Click Start Type Regedit Launch "regedit (run command)" Navigate to and select the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RequestedAppCategories\8b24b027-1dee-babb-9a95-3517dfb9c552 reboot rescan ------------------------- I did 9 without a hitch. fast and easy
of course you delete that entry.... and what does it do. it stops the RETRY again. failure to DL & Install UUPs. for UPGRADE Click Start Type Regedit Launch "regedit (run command)" Navigate to and select the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RequestedAppCategories\8b24b027-1dee-babb-9a95-3517dfb9c552 delete (sorry left that out) reboot rescan
That's not what this thread is about, it's about restorehealth not being able to complete it's task, it's fixed a few weeks ago, by a CU.
Sadly didn't work for me. I did the whole removing registry entries and deleting (moving) the actual packages (.mum/.cat) before I found this thread. I made backups of the registry changes and the files so I simply reversed those, restarted, did your method, but it still fails. This is the output of `dism /online /cleanup-image /restorehealth`: pastebin com/raw/HYL6er4j (add a dot, can't post links yet) Is there any way to find out which package dism is complaining that it cannot find? Edit: Looking at the last part of CBS.log (pastebin com/raw/d5VknRVD) it looks like it's not finding MapGeocoder.dll, MapRouter.dll and InstallAgent.exe in the downloaded files. Any ideas why?
The latest updates supposedly fixed it and when I run DISM on offline image - it passes, but once OS is installed - DISM ScanHealth fails, even on stock image with latest SS and CU... 14393 is officially the last good build of Windows 10.
Yeah, I'm on build 15063.413. Does it fail on those same files for you? I'm asking because I'm actually recovering from a bluescreen bootloop that I solved today removing the TestRoot stuff. These are the files that are trying to be repaired: 2017-06-30 22:11:41, Info CSI 00000007 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.15063.332_none_a873692070dccb9f\MapGeocoder.dll do not match actual file [l:15]'MapGeocoder.dll' : Found: {l:32 znqtT/IYPrzEXJg4OptQddQoeCVOMP6saj/c50EJ1s8=} Expected: {l:32 QUfB3RQ6ZMT6mOM8FS42SjRfdHUEzDclaLkBOvEAKmI=} 2017-06-30 22:11:41, Info CSI 00000008 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.15063.332_none_a873692070dccb9f\MapRouter.dll do not match actual file [l:13]'MapRouter.dll' : Found: {l:32 gFnLA3bRKk4a3WVPVRgX9ixB0sy4XT1rUbmZig1DMp0=} Expected: {l:32 sPHESmVep5TIUK0WW/1sw3FqoFjQMhGBC4dCOzUGWkg=} 2017-06-30 22:11:49, Info CSI 00000009 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-w..client-installagent_31bf3856ad364e35_10.0.15063.332_none_7ef05c0b6a468524\InstallAgent.exe do not match actual file [l:16]'InstallAgent.exe' : Found: {l:32 OAhxUwh26l3E1teNFvnKRb7VYrS9qaVWWZbH3/oGl6Y=} Expected: {l:32 hUNZkaSxXlXRFsTa6Ki5+pVoVdo8F+BcVI3kQO1mQ3Q=}
I simply got the same exact error as before - "source file not found", even when pointing to the Inlstall.wim in a separate directory. It is truly hilarious that for just about every person's problem MS tech support suggests to run SFC ScanNow and DISM ScanHealth. Since DISM ScanHealth often fails for people due to this TestRoot crap, MS suggest to re-install the OS! Then people fall into loops of re-installing the OS, running into some problem not related to DISM, running ScanHealth again, getting the error, and then re-installing OS again per MS advice! Its almost like a deliberate act by MS to mess with people's heads.
Since 15063.332 i never got the "source file not found" message, as part of my real factual tests i run Murphy78's "Windows System File Restore" script on every 1703 June Refresh ISO installs: Win 15063.413 June Refresh ISO Pro x64 install on my testpc: Code: Scanning "D:\Sources\install.wim" to create the index list file... =============================================================================== =============================== INDEX SELECTION =============================== 1. Windows 10 Pro 2. Windows 10 Home ========================== SELECT INDEX OR Q TO EXIT ========================== Please select an Index Number or Q to exit: 1 You have selected Index: 1 Are you sure you wish to use this index? (Y/N): Y ------------------------------------------------------------------------------- Repairing System Files ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.15063.0 Image Version: 10.0.15063.0 [==========================100.0%==========================] The restore operation completed successfully. The operation completed successfully. ------------------------------------------------------------------------------- Finished ------------------------------------------------------------------------------- Press any key to exit... Win 15063.413 Home x64 en-US: Code: Scanning "D:\Sources\install.wim" to create the index list file... =============================================================================== =============================== INDEX SELECTION =============================== 1. Windows 10 Pro 2. Windows 10 Home ========================== SELECT INDEX OR Q TO EXIT ========================== Please select an Index Number or Q to exit: 2 You have selected Index: 2 Are you sure you wish to use this index? (Y/N): Y ------------------------------------------------------------------------------- Repairing System Files ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.15063.0 Image Version: 10.0.15063.0 [==========================100.0%==========================] The restore operation completed successfully. The operation completed successfully. ------------------------------------------------------------------------------- Finished ------------------------------------------------------------------------------- Press any key to exit...
What I don't understand is why would DISM ScanHealth pass without issues when I mount the image offline with DISM++ and run ScanHealth, but it would not pass once the image is online (OS installed) ??? It makes no sense. I am talking about completely un-edited stock MS image.