New
#10
New Windows 10 Insider Preview Fast Build 18346 (19H1) - Feb. 26 Insider
-
-
-
-
New #13
-
New #14
Installing this build was a lot faster to install compared to some of the other builds. I managed to get this build downloaded and installed in just under 43 minutes using Windows Update. I don't know if it made a difference or not but I turned off a few programs that were running in the background. The only security program I left running was Windows Defender.
-
-
New #16
30 Minutes. Not bad.
There is some strange math going on here. Concerning the Reserved Space.
Indications are it thinks it has it, but no physical evidence it does. And odd the total of the drive is larger than the allocated space. No VHDX file showing in Disk Management or anywhere else. Physical partition is 64GB. Reg flag indicates active.
Suspect on next build it will all kick in correctly.
But....... I'm not sure I want it to. I had it set on Skippy with all active and showing the Reserved and all. The next Skippy (18836) took twice as long to process, and went thru 5 loops of Getting Ready, Downloading, Installing - for 45 minutes. After I disabled it on 18336, the next Skippy (18841) went thru normal 1 loop, and processed in <25 minutes. I'm concerned if I leave this alone, the next Fast ring will react the same.
-
New #17
On my systems, going back quite a while now (including 1809), the space reported for C: by settings/system/storage has been off by a very predictable amount. It turns out that the calculation takes any disk space that is occupied by a non-NTFS filesystem (I dual boot with Linux) or an NTFS partion that does not have a drive letter assigned to it, and includes that space in the capacity reported for C:! This has been reported for a long long time, and still no fix. This is flat out bush-league programming, and if I were MS I'd be embarassed to have this issue still unaddressed.
30 Minutes. Not bad.
There is some strange math going on here. Concerning the Reserved Space.
Indications are it thinks it has it, but no physical evidence it does. And odd the total of the drive is larger than the allocated space. No VHDX file showing in Disk Management or anywhere else. Physical partition is 64GB. Reg flag indicates active.
Suspect on next build it will all kick in correctly.
But....... I'm not sure I want it to. I had it set on Skippy with all active and showing the Reserved and all. The next Skippy (18836) took twice as long to process, and went thru 5 loops of Getting Ready, Downloading, Installing - for 45 minutes. After I disabled it on 18336, the next Skippy (18841) went thru normal 1 loop, and processed in <25 minutes. I'm concerned if I leave this alone, the next Fast ring will react the same.
-
New #18
Preparing now. Just saw the news flash. Things do seem to be going more smoothly on the (older!) Lenovo X220 Tablet. I'll report back if I must eat those words.
Best wishes,
--Ed--
-
-
New #19
Update to my post: New Windows 10 Insider Preview Fast Build 18346 (19H1) - Feb. 26 Insider - Page 2 - Windows 10 Forums
Got rid of 99% of it by setting Reserved .reg switch to "0" and doing an in-place upgrade with the ISO I had made, right over top of it, simulating a new build process. No indications anywhere now of any Reserved Space set aside for anything. Still have that space reported on C: anomaly as stated by sgage above. That seems to be an MS quirk. But, I believe I have the Reserved Space in permanent shut-up mode. For now.......
I don't need or want that.
Quote
Related Discussions
