Windows 10 April 2018 Update now available Monday, April 30

JSheridan said:

And System Restore is broken again. It doesn't even work in Safe Mode with this 'update'. Thank goodness for Macrium. :)

Since you have Macrium , there is no need for system restore, it never works as designed in any OS.

ddelo said:

BTW Craig, I did it 0, instead of 1, according to this

EDIT: If you want to have the same Feedback frequency option, as in 1709

Attachment 187005

you can either run both the following commands, from an elevated command prompt:

Code:

Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" -Name "ManagePreviewBuilds" -Value '1'
Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" -Name "ManagePreviewBuildsPolicyValue" -Value '0'

or if you don't want to mess with the registry, and have Windows 10 Pro, you can go to
gpedit > Computer Configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business > Manage Preview Builds and set to "Enable"
and in the 'Set the behavior for receiving preview builds' set it "Disable preview builds", as shown below

Start or Stop Receiving Insider Preview Builds in Windows 10 Windows 10 Tutorials

Attachment 187004

Cool... nice one - hopefully the commands work on Home.

pietcorus2 said:

Superfly ; " but does not hide it as such "...………...yes, just tested your second solution , it works allright .
I can not notice any difference between first- and second solution , it would be awsome if it could start-up minimized or hidden !!
Now we get a very wide blue Powershell-screen , just after booting ( about 5 seconds )

We have a very nice Win10 , this is one of the few things I like to fix , Im even willing to give a reward for fixing it !
You name it , I will give it...……..!!!

After some more testing ,decided to use first solution , coz second one failed sometimes .
If we could only fix this big ,blue screen just after booting ………….

btw; still dont know what triggers this regkey to change after every reboot, this started with RS4-1803...……

There are lots of enforced stuff in Windows 10, activation checks, Windows update etc that reset themselves.
MS are determined to have a system run as they intended. It may be wise to check what that new code means (IIRC it was just 0 or 1 before?)

Here's a fix for the "Big Blue screen"...
New Task creator - delete the existing Task and run this
NtfsDisableLastAccessUpdateTask.ps1

Additional file to be added to the Scripts folder (this hides the execution script)
NtfsDisableLastAccessUpdate.vbs

The first version cannot be hidden as it runs the command directly.

Let me know if it still fails...

Geneo said:

I abandoned it a long while back - it never worked reliably and could not be counted on. For instance, I performed an ie updated, then rolled back, and sfc would give lots of errors.

Macrium incrementals or differentials are 1000x better, 100% reliable, and the delta restore is really quick.

Agreed but RDR and incremental are not in the current free version.

pietcorus2 said:

Superfly , still no luck ; its saying "can not find the vbs-script "...……...first solution still best , so far , except this blue screen after reboot . Im sure now, after testing , this error ( did not excist in 1709 !) appears when starting external HDD .
Maybe this will help you to find the right solution...……...

Are you sure you saved the vbs file to "C:\Users\Public\WindowsPowerShell\Scripts" ?

Anyway seems the codes have changed:
Perhaps it will recognise these codes as 0 and 1 are not applicable any longer.

80000000 → update effective / access date and time
80000001 → Do not update invalid / access date / time
80000002 → update valid / access date / time (default value)
80000003 → Do not update invalid / access date / time (default value)

If the default value is 80000002, wasteful consumption can be avoided by setting it to 80000001. It would be better to keep the SSD force at 80000001.

Source: Google Translate