Windows 10: Announcing Windows 10 Insider Fast Build 16257 PC + 15237 Mobile

This is from Event Viewer:
Code: <EventData> <Data Name="BugcheckCode">239</Data> <Data Name="BugcheckParameter1">0xffffd58b21e8d5c0</Data> <Data Name="BugcheckParameter2">0x0</Data> <Data Name="BugcheckParameter3">0x0</Data> <Data Name="BugcheckParameter4">0x0</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">1</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> <Data Name="BugcheckInfoFromEFI">true</Data> </EventData>[/quote]

 

I like how Edge looks with acrylic with that "softened" noise layer, it is a much more "clean" blur, in addition in this build were added more light effects on Settings:

 

Updated using setup.exe keeping apps and files. Well, apps were sorta kept. Some had to be re-installed to reconfigure options, like Kaspersky Free, some had to be completely reinstalled, like Chrome. I just had reboot from the Boot It Bare Metal CD to reactivate my multiboot which actually took 2 more reboots before the Windows Loader program was working. Sounds bad but actually, it wasn't. So I think I'm happy with this build and can continue with upgrading VMs.

 

Mine has gone 7hrs without showing the reboot message (at installing 85% now)
These updates aren't easily achieved on this old Dell lappie

 

Nope. And Windows is not the only OS obsoleting perfectly good but older PCs - some Linux flavors do this as well. (For example many distros are just not producting 32-bit versions of the OS anymore)

 

second try and the same Green Screen... each try takes 4 hours only to get to the first rebooting screen, so I think I'm done with this build *Sad nevermind

 

When I read 45 min completed upgrades I am like ' wh-wh-wh-whatttt?', lol.

 

Caught me napping, literary. Checked updates only this morning, 6.30AM local time. Doing it now. I don't know if this was the reason I didn't get notification but my date and time were set wrong AGAIN. Date was back by one day and AM-PM were mixed up. I wasn't using any Linux last two days so it can't be that. It only took turning date and time on manual settings and going to time-date update. After that turned auto again and it's fixed.

 

The download and install went faster than usual but had one strange occurrence. After final reboot, Surface 4 hung on the lock screen after Windows Hello recognized me. A manual reboot seems to have cured that.

 

OK. everything updated without a hitch. Usual delays at 76 -78% at first stage but update itself after restart barely 15 minutes. This is skipy one and update folder is 0091e7353fad3039da41c4d5003cf9c3 from which I made ISO. Before doing cleanup I found same thing in windows.old and successfully made ISO out of it too.

 

I don't see any new features at all.

 

19min from windows logo to login screen.
PC restarts about 2 times.


Conditions:
after pressing restart now the system prepares for the upgrade, then resets. The PC goes through it's post initialisation.
I time it after the post initialisation (raid controller takes a while to initialize hard drives after a reset) as the windows logo appears.

 

UUPtoISO presumably?
I found Sophos was blocking it too, so it's not just one AV product that objects to it.

 

I have no other comment than to repeat what I have posted earlier in tutorial thread:

 

1hr 15mins to download and install
now ready to restart