Awesome, it works, thank you very much!!!
1) I restored both of the exported-deleted Registry keys, thanks @gommace for the reg-tricks!
2) After rebooting I exported+deleted the right keys this time!
3) I rebooted.
The results:
Thank you @Eagle51 and @gommace for your solution and support! :)
@Brink, wouldn't you like to have a look at this? :)
It's still not really working as expected.
1. I also first deleted the wrong keys. Although browsers were working fine again, dism failed;
2. Replaced, correct ones deleted. But reboot got stuck at 'configuring windows' - > hard reboot. Then performance issues, but dism restore worked. And now Browsers won't work again...
Hi,
Did you import the exported keys afterwards (I now see you did) and run DISM again ?Awesome, it works, thank you very much!!!
1) I restored both of the exported-deleted Registry keys, thanks @gommace for the reg-tricks!
2) After rebooting I exported+deleted the right keys this time!
3) I rebooted.
The results:
Thank you @Eagle51 and @gommace for your solution and support! :)
@Brink, wouldn't you like to have a look at this? :)
I'm asking because this trick sounds like side-stepping the issue. With all due respect to the person proposing it, it does not make sense to me.
Cheers,
Last edited by fdegrove; 17 Apr 2017 at 02:43.
I completely agree. If we come to understand the problem better, define it as ignorable, I'm okay with a workaround to allow DISM to complete its tasks. I don't think this is the case.
I'm going to dig into PowerShell and have it show all installed packages/components. Perhaps this will yield some results while removing/including the Insiders program
Wouldn't it be better just to wait for Microsoft to fix it eventually, I know they are bad about this but they usually fix the issue.
Initially, I have deleted the wrong keys. Those I have restored.
Then I deleted the right keys (see post #39). Those I have not restored. Those I have deleted from my system.
I have not faced any issue. I am not facing any issue, and I will not face any issue -- that is my belief.
- Can you prove to me that the keys I have deleted from my Registry and from my system, completely, will provoke any problem to me? Please use facts. Otherwise, please do not bother. All I did was to prove with screenshots that in my system DISM works, the way it works. I have NOT suggested this to anyone!
As for waiting for Microsoft to fix this.... I think that this issue has been reported a lot and it is present for quite some time now... Not sure...
I AM SURE about another issue though: after each upgrade the NVIDIA driver has to be re-installed or clean-installed, due to the crippled openCL.dll files, in System32 and SysWoW64! I have shown this, very recently, with screenshots!
Use DISM to Repair Windows 10 Image - Page 40 - Windows 10 Performance Maintenance Tutorials
Do you know for HOW LONG this issue exists?? Personally, I have reported this MONTHS ago! In my Feedback Hub I have this report, and others reported it as well, and we are all upvoting, and reporting, and an Engineer from Microsoft has been informed or something like that and NVIDIA has also released a Creators Update driver!
And still, I needed to clean install the driver...
So, yeah, thanks for your patience.
Last edited by Joanne; 17 Apr 2017 at 07:39.
Hi,
My main point is that DISM isnt working properly leading people into believing there's something wrong when there isn't.- Can you prove to me that the keys I have deleted from my Registry and from my system, completely, will provoke any problem to me? Please use facts. Otherwise, please do not bother. All I did was to prove with screenshots that in my system DISM works, the way it works. I have NOT suggested this to anyone!
Provided SFC /SCANNOW is not returning any error then all is fine.
Dism actually does find the source, it just does not find the refrence it's told to look for, that's all.
Cheers,
Quote