Countless years would be more like it to find out what is dependent on what. Microsoft has always failed to publicly document the dependencies... In ntlite Nuhi is tiring to connect the dots for...
Type: Posts; User: ibach
Countless years would be more like it to find out what is dependent on what. Microsoft has always failed to publicly document the dependencies... In ntlite Nuhi is tiring to connect the dots for...
And... as a matter of a fact... Yes you do have some of the insiders preview there. look here: thread Not that it has anything to do with your problem. Dism might do the difference. Read the thread...
Guys,girls...
Disable windows defender.
Have a nice day!
PS all of the modern apps as some are calling those are a primordial bloatware. F** those.
Bree... I was merely explaining wim-esd general differences. Nothing of what I have said in my last post has a thing to do with this particular error. So I do not understand "Not quite, apparently."...
You can use either wim or esd image for what's the format concerned.
For more info look HERE
For ESD:
Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:Full Path to install.esd file:1
or...
Thank you people! Laughing here too!
Remove all the files mentioned and registry entries. RESTART is mandatory for the changes in registry to work.
Do the manual or MonarchX way no matter.
so to recapitulate:
all the instances of...
Yap. The moment that grapes start growing on willow trees.
Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4016240)
fixed nothing.
BTW it seems that those files are there...
What is the "but" word for in this sentence? You mean it did not screw up windows, don't you? "and" would be more like it.
Thanks for the post though ;)
After some more analysing...
Used MonarchX method to uninstall the package. It did work.
Two more files I've found on HDD afterwords....
I've noticed that the problem does not occur in all the cases.
If installed with update assistant on a machine that has windows 10 updated (all the updates until today) and whose image is healthy...
The one by MonarchX
The "ToBeUninstalled" entry in that post should actually be: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based...
those would be in:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\CatalogsToUninstall
Ps:
Thank You MonarchX! Those tools are cool. And... 4.0's...
and as usual ... there is a better method by someone smarter than me... lass destructive and hazardous.
Please use the same method for other offending packages too. Follow the link:
Creators update...
and only to often it does.
This will happen if there are Windows Packages Files installed that are not on the install image or, as in Windows Creator update from April 2017 image, there are some...
If any of you has Avast AV and trouble fixing image, stop Avast self defence module and all 3 shields. Try fixing again. Worked for me.