KB4100375 Windows 10 Insider Release Preview Build 17133.73 - Apr.10 Insider
-
I have to re-time it once RTM is official. I will test on physical machine (not VM, which I use now)...fastest I've got so far is from Opening up WU to full reboot and to upgraded desktop was about 35minutes. That is on my old Tractor of a laptop. :)
30 minutes is offline time and I have done several tests and that is more or less the time it takes in hard drives:
-
-
30 minutes is offline time and I have done several tests and that is more or less the time it takes in hard drives:
LOL, offline time is less than 10 minutes for me, on VM or no VM.
-
This is RTM if nothing really bad happen. Microsoft is always playing such games. Pretending that "RTM" build is just another build. Look back at "RTM" builds blog posts from previous releases.
Of course this RTM. I will be doing a clean install later.
Windows 10 Redstone 4 reaches RTM milestone | Windows Central
-
But that is the only time it is not available for other work. They have been moving more of the upgrade process to before the restart to achieve this.
HOE LEA MOW LEA - It took my laptop only 12 minutes or so from restart now to being fully installed. This is a major improvement - MS have got this one really nailed down! My flabber is truly ghasted.
-
-
LOL, offline time is less than 10 minutes for me, on VM or no VM.
I guess that each case is different, that's why they talk about average time, in my case, in traditional hard drives, it takes 20 to 30 minutes that process.
-
I guess that each case is different, that's why they talk about average time, in my case, in traditional hard drives, it takes 20 to 30 minutes that process.
Yeah, I'm on SSD...but it's getting really slow...need a new computer with better hardware :)
-
I stand corrected (slightly), it took me 8:42 from clicking restart to desktop.
-
I have been waiting until now to be sure, but in the IP releases, I have been having issues accessing my Netgear NAS (ReadyNAS 214). It seems that unless I have the IP address and name entered into the "C:\Windows\System32\drivers\etc\hosts" file, the Netgear, while visible in FileManager, cannot access ANY folders or files on the device. Once the IP/Name is entered, everything is OK.
Does anybody have any suggestions on how this might be fixed?
FWIW, I have both Buffalo NAS (LS421DE & LS441DE) devices in addition to the Netgear that do not have any problems like this.
-
Done fastest yet one hour and eleven minutes from start to a desktop.
-
-
17133 is now in GitHub uupdump.
Quote
