Announcing Windows 10 Insider Preview Fast Build 16294 for PC Insider

AndreTen said:

Background image was from Storage (in Settings). Disk cleanup was giving much more accurate numbers. (I know where to look at :))

Your Background image was from Disk cleanup....see Storage attachment, by clicking on each bar gives a comprehensive breakdown of everything loaded on the computer
If you read my post again it had nothing to do with Disk cleanup...don't take it as a personal slight, others beside yourself read these comments.

cereberus said:

Well it nearly worked - created small windows.old on c drive with large window.tmp file on usb drive. Used about 65% of battery.

However, none of the action items in task menu worked. Will try a rollback once recharged out of interest. I that fails, good old Reflect to the Rescue.

Why do some updates - like 16291 - keep changing (kill) my Windows 10 Insiders settings to abort mission: Unlink MS account -> Link MS account again?



DL...

tinmar49 said:

I'm still on 16281, having several attempts to load 16288 fail, I abandoned the TP and continued with a standard W10.
Now the new 16294 has arrived, I have switched back to the TP, but it is still trying to upgrade to 16288, rather than skip directly to 16294.

Make sure your settings states that you are on Fast Ring (not Slow Ring). Also empty C:\Windows\SoftwareDistribution\Downloads\ folder completely and after a reboot, try again.

Kari said:

As far as I know the only way to check the actual, correct time of original install before any subsequent in-place upgrades is to to enable showing protected system files and folders in Explorer, then check the properties of pagefile.sys and / or swapfile.sys. This shows the creation date of these files; the files were created when Windows was first installed after last time C: partition was formatted, when Windows was clean installed:
Kari

Thanks Kari - this is the properties shot of the pagefile.sys - swapfile.sys is the same.
The reason for 9/21 date is I restored an image of the OS to the drive yesterday. Pretty sure Acronis erases the disk before installing the image.
Thanks again - another tidbit of info to add my "info collection"

Following earlier discussion of the benefits of retaining the Windows.old folder or ditching it, some have experienced the upgraded version using files that exist in the Windows.old folder or more serious anomalies.

In many cases it has been the graphics driver files, although I have recently experienced a creator's 1703 version that had been getting slow & unstable, and could not sustain any updates to insiders builds without rolling back, with a final ditch attempt to retrieve the installation with a reset before attempting an update to the latest insider build. However Windows.old was still too large to allow an update, and could not be removed by Windows clean up due to many files currently open in the windows system. Deleting Windows.old from an external Linux system resulted in a largely non-functional Windows system, booting to a black Windows explorer with mouse pointer, a mostly blank taskbar, and no taskmanager after the ctrl-alt-del security options screen.