Releasing ISOs for Windows 10 Insider Preview Build 10130 Insider

Releasing ISO so much later than ESD is pure BS if you ask me, why to slow ring ? If any of us are able to convert ESD to ISO in few minutes, how come all those smarties at MS can't ?

CountMike said:

Releasing ISO so much later than ESD is pure BS if you ask me, why to slow ring ? If any of us are able to convert ESD to ISO in few minutes, how come all those smarties at MS can't ?

They delay the ISO's because they want you to upgrade instead of clean install. Pisses me off too. MSDN still only shows 10074. The last couple of installs for me were, Windows 7 or 8 upgraded to 10074 upgraded to 10122 upgraded to 10130. I decide to do it their way to see what happened. The upgrade from Windows 7 is still in use but the upgrade from 8.1 on my laptop got nuked due to driver issues.

I've been testing the whole time using my SSD, but since GWX has been activated, I re-imaged with Win7 back to it last week, so it can start working it's magic. Today I pulled out the 5400rpm HDD that came with the laptop, and put the Macrium image on that(Damn is that disk slow, been using only SSDs for the past 4 years:)) . After re-imaging I ran winsat formal in Admin CMD & rebooted so Windows can make the adjustments necessary. Now I'm defragging(Windows own defragger of course) and It's a lot slower now (duh!) but runs well.

Cliff S said:

I've been testing the whole time using my SSD, but since GWX has been activated, I re-imaged with Win7 back to it last week, so it can start working it's magic. Today I pulled out the 5400rpm HDD that came with the laptop, and put the Macrium image on that(Damn is that disk slow, been using only SSDs for the past 4 years:)) . After re-imaging I ran winsat formal in Admin CMD & rebooted so Windows can make the adjustments necessary. Now I'm defragging(Windows own defragger of course) and It's a lot slower now (duh!) but runs well.

Likely a 5400 RPM drive, that will make things even slower.