ComputerWorld Says Newest Windows 10 'Isn't Ready for Prime Time' (computerworld.com)

"Despite Microsoft's assurances, Windows 10 1803 isn't ready for prime time," writes ComputerWorld's Woody Leonhard, adding "Microsoft's patches in June took on some unexpected twists..." Win10 1803 was declared fully fit for business, a pronouncement that was followed weeks later by fixes for a few glaring, acknowledged bugs -- and stony silence for other known problems. We're continuing the two-big-cumulative-updates-a-month pace for all supported versions of Windows 10. The second cumulative update frequently fixes bugs introduced by the first cumulative update. Microsoft may think that Win10 (1803) is ready for widespread deployment, but there are a few folks who would take issue with that stance...

Tuesday, Microsoft finally released a fix for two big bugs that have dogged Win10 1803 since its inception... In practice, life isn't so simple. WSUS (the Windows Update Server software) isn't "seeing" KB 4284848, as of late Wednesday afternoon -- which may be a good thing. Along with the second cumulative update this month, there are additional releases to fix the Servicing Stack, and a new "Compatibility update" that, per the documentation, is designed to make it easier to upgrade Win10 1803 Enterprise to Win10 1803 Enterprise (not a typo)...

One problem that has been acknowledged -- but only by a Microsoft Agent on an Answers Forum post -- says that installing 1803 can clobber your peer-to-peer network. That certainly matches my experience.
Woody concludes, "If you think Win10 1803 is ready for prime time, you're welcome to give it a try."

Comments

Doesn't matter

[Waffle Iron]

Ready for prime time or not, I'm sure it's going to show up real soon on my system in another ambush upgrade.

(Hint to MS: I set the computer to "Hibernate" because I was expecting to come back and pick up where I left off *quickly*. I specifically did not want to come back to find "Windows is finishing updates. Do not turn off your PC" for 45 minutes instead, followed by having to recover all of the open files that got trashed.)

Re:I have no Windows 10 issues at all

[Anonymous Coward]

Me neither. When I first installed it (during the 'get it free' era), it suddenly maxed my 'net connection; after 15 minutes or so of continuous, unauthorized, unexplained, massive net traffic, I powered the system down. I then scrubbed the drive and reinstalled Windows 7 from backup (I use commercial CAD software, gotta have Windows, no choice. 7 works fine, no changes required minimum of newly undiscoverable UI BS ).

I have no problems with W10 and don't foresee having any until such time as i am forced to install it.

Re:Excel bug will not save any old .XLS files

[LVSlushdat]

Dunno WHY I'm replying to an AC, but in the case of said XLS that Windows has decided it doesn't want to handle anymore, you might try LibreOffice. I deal with some small businesses that, for one reason or another, have to continue to use Windows/Office. One of them a while back had an Excel spreadsheet that was older than the hills, and the Office2013 installed on the machine in question, did not like this spreadsheet AT ALL.. Since I only use Linux/Opensource stuff on my personal systems, I decided to copy the xls to a memstick and tried opening/saving in LibreOffice 6.. Was able to open/modify/save said xls just fine, and as a bonus, WHATever Office didnt like about the xls before, once LibreOffice did its thing, the "fixed" xls was now working fine under Office... Go figure..