![]() ![]() There have been many reported problems with this month’s.The block was lifted – but apparently nothing was changed. Microsoft was blocking August Win7 patches on systems running Symantec/Norton antivirus, apparently because of the shift to SHA-2 encryption, which has been widely anticipated for six months.We’ve had loads of additional fun ‘n games this month: Nice choice, eh? From the oldies but goodies file Or you can hold back on patching, keep VB working, but leave your system open to a DejaBlue infection. Until Microsoft releases a fix for the VB/VBA/VBScript problem in Win10 1903, you have two choices – either patch, protect yourself from DejaBlue, but break VB. Of course, plenty of people are trying to build them. As of this moment, there are no publicly available DejaBlue exploits. While I’ve read lots of Chicken Little reports that DejaBlue has been exploited, none of those warnings has come true. While DejaBlue simmersĪll of this would be frustratingly academic, if it weren’t for the fact that DejaBlue – a new set of “wormable” security holes in Windows itself – made its debut this month. Regardless of the genesis, those of you waiting to get a fix for the VB/VBA/VBScript problem in Win10 version 1903 will have to wait a little longer. ![]() It looks like we’re waiting until Microsoft gets the bifurcated patch to work on both Win10 version 1903 and on the beta of version 1909. In particular, the 18362.327 preview of the Win10 1903 patch went out at the same time “the 10%” got a Win10 1909 patch called 18363.327 (see how 18362 changes to 18363?)Īpparently that build wasn’t good enough, so on Aug. Some of those versions are being distributed to people who are in the Release Preview ring. That seems complicated, but reasonable enough – until you realize that the Win10 1909 beta currently has eight differ ent versi ons. After the update finishes, they will be on version 1909 Build 18363.327. They will be able to choose to download and install this update on their PC. For these Insiders, if they go to Settings > Update & Security > Windows Update, they will see that there is a Windows 10, version 1909 update available. 26:įor a small subset of Insiders (around 10%) in the Release Preview ring, we have enabled the “seeker” experience for version 1909. That’s great – it’s what the Release Preview ring was made for.ĭuring the month of August, though, the Microsoft beta people took over a corner of the Release Preview ring and pushed the beta version of 1909 onto (supposedly) 10% of the 1903 testers. But this month it looks like we had a significant divergence of direction.įor the past year, Microsoft has been testing its Win10 1903 patches thoroughly, using the Windows Insider Release Preview ring. Normally, beta testing doesn’t have much of an influence over month-to-month patching. The unholy mess that is Win10 1909 beta testing We still don’t have the second August cumulative update for Win10 1903 – the one that’s common called “optional non-security,” with varying degrees of accuracy. It’s not clear why, but I have a guess that Microsoft’s so wrapped up in beta testing Win10 1903 that it somehow fell through the cracks. 30, we still don’t have a fix for Win10 1903, the latest version of the last version of Windows. 19, Microsoft released a fix for:Īs of today, Aug. 16, three days after Patch Tuesday, Microsoft released fixes for the bug in: If you’ve been following the details, you know that on Aug. I think of it as Patching as a Keystone Kops Service. The bug affects every single version of Windows – all the way from Win7 to Win10 version 1903. More importantly, many large corporations’ internal custom programs turned belly-up. Some companies’ commercial applications stopped working intermittently. Folks running applications in any of those languages would, on occasion, receive “invalid procedure call error” messages when using apps that had been working for decades. Microsoft somehow managed to mess up Visual Basic (an old custom programming language), Visual Basic for Applications (for Office macros) and VBScript (a largely forgotten language primarily used inside Internet Explorer). No doubt, you recall the first wave of pain inflicted by the August 2019 patching regimen. What happens when Microsoft releases eight – count ‘em, eight – concurrent beta test versions of Win10 version 1909 without fixing bugs introduced into 1903 on Patch Tuesday? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |