News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon

Blog Archives

  • Yet another bug in Win10 1803

    Posted on August 17th, 2018 at 11:22 woody Comment on the AskWoody Lounge

    This was just added to the “known issues” section of this month’s cumulative update for Win10 1803:

    Symptom Workaround
    Launching Microsoft Edge using the New Application Guard Window may fail; normal Microsoft Edge instances are not affected. If you’ve experienced the issue and already installed KB4343909, uninstall it.

    1. Install KB4340917.
    2. Install KB4343909.

    Microsoft is working on a resolution and will provide an update in an upcoming release.

    Yes, that’s exactly what it says… install KB 4343909 again.

  • Win10 1803 Aug cumulative update: Installation fail loop ”Update couldn’t apply, reverting changes”

    Posted on August 16th, 2018 at 10:28 woody Comment on the AskWoody Lounge

    Looks like this problem (which has occurred with every version of Win10, as far as I know) has reared its ugly head with the August Win10 1803 update.

    Uroboros4 on Reddit says:

    I have Win10 1803 genuine. None of the cumulative updates can be applied(for example KB4343909, kb4284835, kb4103721). It reaches 100% and says ” Update couldn’t apply, reverting changes”. I have tried a lot of stuff (pausing win update and manually installing them, scan windows for corrupted files to no avail). Anyone has the same problem?

  • Patch Tuesday hits with a bang

    Posted on August 14th, 2018 at 12:20 woody Comment on the AskWoody Lounge

    The Microsoft Update Catalog suddenly lists 116 separate downloadable patches, dated either Aug 10 or 11.

    Martin Brinkmann has his usual thorough review on Ghacks of the August patches:

    • Microsoft released updates for all versions of Windows, Microsoft Edge, Internet Explorer Microsoft Office, and other company products including Visual Studio, .NET Framework, Microsoft SQL Server, Microsoft Exchange Server, and Adobe Flash Player.
    • All client and server versions of Windows are affected by critical vulnerabilities.
    • Microsoft does not provide a general overview of resolved security issues anymore on support pages.

    Former ‘Softie patching guru, now working for the Zero Day Initiative, has details:

    Microsoft released 60 security patches for August… 19 are listed as Critical, 39 are rated Important, one is rated as Moderate, and one is rated as Low in severity. Twelve of these CVEs came through the ZDI program. One of these bugs is listed as publicly known at the time of release and two others are listed as being under active attack… 13 of the 20 Critical bugs affect [Internet Explorer and Edge]

    Looking through Childs’s list, the only currently exploited “Critical” security hole is in Internet Explorer. The second currently exploited security hole is only rated “Important” which means, of course, that it isn’t.

    The Win10 1703, 1709 and 1803 patches still list this known bug:

    After you install any of the July 2018 .NET Framework Security Updates, a COM component fails to load because of “access denied,” “class not registered,” or “internal failure occurred for unknown reasons” errors. The most common failure signature is the following:

    Exception type: System.UnauthorizedAccessException

    Message: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

    So it looks like MS still hasn’t fixed the .NET bugs from last month.

    Patch Lady Susan here with a late Tuesday evening update to this post:  Microsoft has updated the known issues section and removed the sections about the .NET/COM errors that were listed in July.  In my early testing I haven’t seen side effects but I will be doing more testing/more watching.  So for now hang loose and test and wait.  Clearly they messed up the documentation in this month’s release and copied and pasted the text from July’s releases.   The only known issues left are the ones with Exchange (make sure you install with admin rights) and the missing OEM note in Windows 7 (shown below).  In ALL of my Windows 7 testing I have had zero issues and my understanding this network interface problem is limited to VMware (virtual machine) installs.  Thus I don’t anticipate that we will see this on normal machines.

    From @PKCano:

    Win8.1 Monthly Rollup –

    Win7 Monthly Rollup –

    The Win7 Monthly Rollup still lists:

    There is an issue with Windows and third-party software that is related to a missing file (oem<number>.inf). Because of this issue, after you apply this update, the network interface controller will stop working.

    More .NET patches. The  main ones:

    • KB 4344145 – Security and Quality Rollup for .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, and 4.7.2 for Windows 8.1, RT 8.1, and Server 2012 R2
    • KB 4344146 – Security and Quality Rollup for .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, and 4.7.2 for Windows 7 SP1 and Server 2008 R2 SP1, and for .NET Framework 4.6 for Server 2008 SP2

    Of course, Microsoft promises that these .NET patches work just fine, unlike last month’s. Susan Bradley has a bit to say about that:

    August 2018 Office Security Updates have been released for Office 2016, Office 2013, Office 2010, the Office Viewers and the SharePoint servers.

    SANS Internet Storm Center has their assessment, which reinforces Childs’s analysis.