When you work in software this seemingly counterintuitive process actually gets good builds out faster. Without deadlines you end up with endless dev cycles were nothing ever feels done enough to release because you always can add just one more thing. A deadline forces you to pick the most critical projects and to finish them quickly.
From my understanding there are two possibilities for SCU official release, right now: 17133.1 (already released in Insiders' Fast, Slow and Release Preview rings) will be kept as RTM, as they found a proper fix to critical-bugs with a new CU that will normally bump up the delta number from .1 (or .73) to something higher .xxx --> In this case SCU could be released as soon as tomorrow for everyone on Production; A new build 171xx.1 (not yet released to Insiders) could be released tomorrow in Fast ring as the new RTM candidate, and then distributed also to Slow and Release Preview ring by the end of this week, along with a first CU that will bump up the delta number from .1 to something higher .xxx --> In this second case SCU could be released by the end of next week (so still by the end of April). I don't have much hope for the first possibility right know, but it could still happen if 17133.1 was actually already distributed to all OEMs and those have already pre-installed it to numerous hardware stocks.
Mine as well. No such issue here. How about connecting the drive, removing it from Device Manager>Disk drives, and removing/reconnecting? Also for research purposes, may I know the brand and model of the drive? Thank you.
I applied the CU on 17133.1 to .73 but result was a sluggish system , as soon as i un-installed it , the system is performing better again, I think still a lot more needs to be done on redstone 4 before its final RTM is released to market.
I don't have any performance lost on my main system. Let me run a test this evening on my test pc, i will install 17133.1 and run a benchmark, next i will install the .73 CU and re-run the benchmark.
Thanks for the advice. Reinstalling the driver fixed the issue after a system restart. For the record, the USB drive was a SanDisk Cruzer Blade.