New
#140
I don't have any problems yet with this update, maybe because I did a clean install of the Windows 10 April Update.
Rebooting doesn't work on all PC's. This same issue happened a couple years ago. It seems that MS never actually fixes these because they don't know what the cause is or more likely they have no intention of fixing it.
Telemetry settings sometimes fixes it which indicates that their spying & data collection is getting more intrusive.
This issue is all over the Feedback Hub. I "Upvote" them all.
The AllowTelemetry entry under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection
was was put there by O & O Shutup 10 (at least in my case). If you remove that entry and reboot you now have access to changing the Diagnostic data to Basic or Full. However it does not remove the red line saying: " * Some settings are hidden or managed by your organization. "
If you remove the entry, the next time you run O & O Shutup 10 it will notice the registry entry was removed and ask to either revert the change or accept the change.
I appreciate the info.
Installed this update this morning ... no major problems .... But something is off .... windows thinks it needs to reboot in order to install this update, even though I have rebooted several times.... Update history shows it was successfully installed .... Update wants a restart or a scheduled restart .... Also shows on the power off list ... update and shut down or update and reboot ....
I recently updated all 3 computers from Legacy to UEFI using MBR2EFI. I now seem to have 2 OS recovery partitions as well as the main Windows 10 OS on my C Drives.
I was wondering if this might be the problem?
I assume one is for the UEFI and the other is the original recovery partition.
Can the other recovery partition be deleted, and if so which one is which?
Just some thoughts, and if any one else with the failing update is in a similar position.
Two computers applied the update this morning and went to a black screen. The third is "locked and loaded" but paused. And I haven't turned on the other two.
Yes, I have can roll back to 1709 via Reflect. But this is ridiculous. Thanks MS.
Problem is in this article:
https://www.windowslatest.com/2018/0...b4103721-bugs/