30 mins to 1 hour usually. isp speed ($$$$) router capabilites, wireless router speed, distance from source and so forth control all the time to completed install. NBD. I didn't clock this one guessing less than an hour. couple minor tweaks and it is running.
I tried a slightly different approach this time on both Fast and Skippy. I've noticed on recent builds there is no longer a Getting Things Ready>Download>installing sequence like past history. Least not here that I could see. What I have noticed is the downloading seems to do a lot of churning while DL'ing, TiWorker and/or Windows Update process. Then sits at 100% after DL finished before starting Install.
This time, I watched Task Manager>Performance. At around 7-8 minutes after boot, Ethernet receive spikes at max bandwidth and CPU climbs high and stays there. Lots of disk I/O, too. Then, around 15 minutes in, all calms down. Net drops to zero, cpu 1-2%, I/O just a trickle. Then I went to Check for Updates and it was sitting at Install Now. Clicked and ran very smoothly with no burps or loops. 20 minutes to first Restart, normal 10 minutes or so for the Working on Updates and Hi! and all that falderal.
Conclusion, if there is one, the "getting things ready" work is being done in tandem with the downloading. That's why it seems even if you have a 200Mbs connection, it's only cranking at an overall apparent speed much slower.
This fix has been added to the flight notes:Another bug with transparencies has been fixed in this build.
Bef:
Attachment 252118
Now:
This is not mentioned in the list of fixes. In the previous build Microsoft had already fixed another bug that also had to do with transparencies.
I had the same problem trying to install new build on my desktop. The first try would fail and the second try would succeed. I fixed it on my desktop by exiting all the programs and apps running in the background that I could. Since then all the builds are installing on the first try.
Edit: That doesn't include the restart problem I had. I had one heck of a time trying to get the build installed because every time I would restart to finish the install I had to hit the restart button and had to go through the whole download and install all over again. MS did release a fix. What finally worked was changing the power setting then changing it back. That allowed the desktop to restart on it's own.
Wow. I have to agree with CountMike. Gaming and graphics performance in this release seems terrible.
I didn't realize just how bad it was until I switched to my Release Preview Install to update and test it out.
On 19008.1 had framerates in the 60-80 (low) fps range, as compared to 120-140 (normal) fps in 18363.449.
This is while playing World of Warcraft on basically the same exact installation setup using driver 440.97.
I understand that there will always be a margin of error in these things but that seems like an awful lot.
19008.1 seems to work fine otherwise. This difference was just something that surprised me enough to share.
peace
wanna
Hey guys, I noticed when I click on settings then the apps page, not all apps are being displayed... anyone else?
Source (copy and paste comment) at https://www.reddit.com/r/windowsinsi...formance_with/
A workaround/fix (which allows users the ability to play "certain" DirectX games in fullscreen):
Right-click on the game's .exe file or shortcut.
Select Properties
Select the Compatibility tab
Enable "Disable fullscreen optimizations"
Apply
OK
I tested few games with workaround method works for me.
Ex.
Project Cars at 57fps without method.
Project Cars at 90fps with method.
Try that method for you to see if it's works.
Quote
