New
#40
For users on 32GB tablets, this would be a good idea, as it is sometimes impossible to update without deleting some apps due to space needed for windows.old.
Obviously, it would require a strong warning to do this and option would only arise if there was not enough space for windows.old. This way for most users, they would see no change, but for a few users it would be a useful option.
An alternative and perhaps better solution would be ability to store windows.old on another drive e.g. USB flash drive or SD card.
I completely disagree. The question is, what is better: to risk completely bricking your tablet because upgrade fails and can't restore the previous version due lacking Windows.old folder and then being forced to clean install, or to manage and maintain your tablet (using external SD card / USB) in such a way that there will be enough space to upgrade and create Windows.old?
Most of these tablets use some storage space for a factory recovery image. In my opinion it's better to remove this recovery partition and use that space for C: drive, then use Macrium to image the device to external target, than to not create Windows.old.
Kari
First time I have seen a Windows.old(1) All those folders are empty.
Wonder if it has something to do with the way this update installed (see post #24)
I also wonder if my use of an NVMe SSD (PCI-E mode) has a bearing, Both the updates since I installed new hardware have had problems. I clean installed 16288 on one of the NVMe drives, both the following updates have acted strangely, with this one to 16294 failing on first attempt. But eventually installing on the second attempt. No video after the second (at 75%) reboot till I powered off and on again, Then no messages about getting things ready, etc and no Hi.
Hyper-V (Import of 10 VM was a breeze) and WSL (Ubuntu 16.04 and openSUSE Leap 42) was perfect.
Really? a branch that is just beginning and you declare it "dead" just because Microsoft has taken a little more than a week to release a build for that branch? several times have been two or three weeks without Microsoft releasing a build and yet people do not declare that branch "dead" only for that, what happens if today or tomorrow Microsoft releases a new build for Skip Ahead?
Even that build apparently has anything new that name implies, it's even behind normal fast builds !! It's more like Skip Back. MS could provide at least some hints about eventual newer features and give us some previews of them, if nothing else at least to peek some interest into it. If none, it's at leas o little bit dead. Presumably it's a start to Rs4 before October 17th. after which it will be actual anyway if insider builds are to be continued at all. So yes, it looks like to be on death bed anyway.
Couldn't really blame them, all resources are tied up in Rs3 finalization but at least a part would be in future development as it does take long time.