+1Neither am I, except I'm not checking. I'm waiting for it to be freely offered ... maybe in October!
I've come to believe that it's appropriate to delay a major update by half a lap unless there is a very big change.
Windows 10's June 'Patch Tuesday' updates rolling out now (1803,1809, 1903, 1909 and 2004)
-
Thread starter
CyberTech
- Start date
- 32 Replies
- 8,762 Views
- Status
I've come to believe that it's appropriate to delay a major update by half a lap unless there is a very big change.
I had a bad experience once with Windows rollback. Backing from 2004 to 1909, but that shouldn't be the case with security updates.
Yes same here by far the slowest update I have ever experienced (like wading through treacle) , for those of you yet to experience it - be prepared for a one hell of a long haul.
I would't rely on any Windows roil back under any circumstances - I image very regularly and as my Windows image is under 12 GIG its a matter of a few minutes to image back if there are issues as all data is kept on separate/partitions/drives - I use Diss + + to reduce winsxs folder/cleanup - I wouldn't recommend this to anyone but it's not caused me many problems in many months maybe much longer - I run it every month or so - Works fine for me - You can also use a command in CMD.
Last edited:
Avast fixes bug blocking programs from starting in Windows 10
A bug has been fixed in AVG and Avast security applications that set registry keys that blocked applications from running in Windows 10.
It may have been a new feature that prevented the execution of any program.Avast fixes bug blocking programs from starting in Windows 10
A bug has been fixed in AVG and Avast security applications that set registry keys that blocked applications from running in Windows 10.www.bleepingcomputer.com
With updates paused AND a metered connection, I downloaded the SSU and June CU from Windows Catalog and installed them manually to see if things went faster than the usual 2 hours for updates on a low-spec 1909 laptop here. Excluding the download (which I did on an Android tablet), the installation took 35 min., including reboot, and went smoothly.
This is about printers issues
M$ should have a new song: "(Music playing) One little bug in 2004, two little bugs in 2004, three little bugs in 2004 ... and the bugs keep comin' along!"
Is this the worst update yet? Even worse than the version that deleted users' files (I forget the version #)? I guess it depends ...
Well, I agree: 2004 is a hot mess right now. But 1909 was awesome, I thought.
It's baffling why this mess couldn't pick up where 1909 left off. It's like all that telemetry we Insiders were providing ahead of time made not one jot of difference. The same bugs that were actually FIXED in later Insider builds are back plus all their friends and neighbors. Disgusting.
I do believe, however, that enabling Full telemetry during the first few days of 2004 was helpful in reducing errors and other problems. For example: the initial cascades of ESENT 642 warnings in Event Viewer decreased markedly-- I'm only getting 2 or 3 a day now. I know: telemetry is a four-letter word. But it's beneficial in some limited contexts.
It's baffling why this mess couldn't pick up where 1909 left off. It's like all that telemetry we Insiders were providing ahead of time made not one jot of difference. The same bugs that were actually FIXED in later Insider builds are back plus all their friends and neighbors. Disgusting.
I do believe, however, that enabling Full telemetry during the first few days of 2004 was helpful in reducing errors and other problems. For example: the initial cascades of ESENT 642 warnings in Event Viewer decreased markedly-- I'm only getting 2 or 3 a day now. I know: telemetry is a four-letter word. But it's beneficial in some limited contexts.
- Status
Recently browsing
Members who viewed this thread in the last 5 minutes
