Woody Leonhard's no-bull news, tips and help for Windows, Office and more… Please disable your ad blocker – our (polite!) ads help keep AskWoody going!
Home icon Home icon Home icon Email icon RSS icon
  • Patch Lady – .NET previews but…..

    Posted on May 16th, 2018 at 16:53 Susan Bradley Comment on the AskWoody Lounge

    So this is the third week of the month when normally we should see previews for next month’s 7 and 8 platforms.

    ….and   well the word “normally” is actually a misnomer as we have no real normal anymore.

    We do have a .NET preview for next month:


    I’ll be updating the master chart list accordingly.

    We do not have a Windows 7 or 8 preview (yet) so I’ll keep my eyes peeled for any 7 or 8 preview updates that “normally” should be out yesterday.  We are still tracking networking issues in Windows 7, and 1803 still is to be deferred.

    As an aside I’ve seen a fair amount of HomeGroup folks impacted by the removal of HomeGroup in 1803.  If your devices suddenly can’t see one another try this:

    Go in the control panel, then into services.  Find  Function Discovery Resource Publication, and set it to automatic and start the service.


  • Patch Lady – KB4103718 /KB4103712 known issues

    Posted on May 14th, 2018 at 13:41 Susan Bradley Comment on the AskWoody Lounge

    As noted in https://support.microsoft.com/en-us/help/4103718/windows-7-update-kb4103718 and in https://support.microsoft.com/en-us/help/4103712



    Microsoft is aware that some customers have reported that network drivers are intentionally uninstalled, then fail to reinstall after applying the May 8, 2018 update. This can result in the loss of network connectivity. Microsoft is presently investigating and will provide a status update when the investigation is complete.
  • Patch Lady – an ask for a Friday

    Posted on May 11th, 2018 at 16:01 Susan Bradley Comment on the AskWoody Lounge


    Please if you are running a Windows 10 machine, I’m asking for your help in upvoting this.  My feedback on Windows is quoted below:

    “On behalf of your customers and the security ecosystem of Windows 10 please take this feedback seriously: Please review the procedures and policies you have in place for servicing.

    Surface devices should not BSOD on 1803. Enterprise detection of May updates should not need metadata revisions. We should not be losing Nics in various platforms. We should have trust in the updating process that would let us feel comfortable in installing updates the week they come out not mandate that all of us are waiting and seeing what issues occur.

    We, the patching community, your customers have lost trust in your patching processes. Please, please fix this. Ensure metadata issues do not occur. Ensure better quality testing is done. Ensure feedback processes are strengthened so that customer feedback is acted upon BEFORE issues occur not after Microsoft themselves have to acknowledge the issues.”

  • Patch Lady – if you do have 1803

    Posted on May 9th, 2018 at 23:25 Susan Bradley Comment on the AskWoody Lounge

    If you do have 1803 on your computer systems, you’ll honestly want to install https://support.microsoft.com/en-us/help/4103721


    There are several key fixes in this release:

    1. The issue impacting Chrome and Cortana is fixed.  “Addresses an issue that may cause some devices to stop responding or working when using applications, such as Cortana or Chrome, after installing the Windows 10 April 2018 Update.
    2. Fixes an issue with interaction with Server 2016 Essentials and those who have VPN set up.  The issue manifests itself whereby the Server connector software can’t be installed on 1803 machines if VPN is set up on the server.  Installing this update fixes the side effect.  It may also fix issues with third party vpn software.  “Addresses an issue that prevents certain VPN apps from working on builds of Windows 10, version 1803. These apps were developed using an SDK version that precedes Windows 10, version 1803, and use the public RasSetEntryProperties API.
  • Patch Lady – early trending issues with 1803

    Posted on May 3rd, 2018 at 15:06 Susan Bradley Comment on the AskWoody Lounge

    I’ll be updating this post with trending 1803 install issues I see and potential resolutions:

    I will note when an issue is expected and when (to the best of my knowledge) it’s not expected.

    1. Home group removed:  Known and expected:   Microsoft has removed this from 1803 and recommends alternatives:  https://support.microsoft.com/en-us/help/4091368/windows-10-homegroup-removed
    2. After 1803 seeing several reports of recovery drive being assigned a drive letter.  Not expected.  Workaround:  Use Diskpart to remove drive letterAcknowledged by Microsoft.
    3. Alienware laptops and desktop users are reporting issues with the upgrade.  Expected this is actually a block with a not well thought out error message  Not expected.  Workaround:  Per page 3 on this forum.  Remove Alienware update and digital delivery utility and just leave Alienware command centre and Alienware onscreen display.  Alternatively you can download from the media creation page,  when it proceeds to “creating media” disconnect from the Internet and it will prevent it from downloading drivers and will get past the 49% mark where the install gets stuck.   UPDATE see https://www.askwoody.com/2018/patch-lady-dont-go-around-the-block/
    4. Chrome is freezing after the update as noted here:  Known issue.  Fix now released install the May 1803 update.
    5. For those running Essentials 2012 R2 or Essentials 2016 (Microsoft’s SMB server) the connector software that needs to be installed on Windows 10 to get it to communicate fully with the server is having issues with 1803.  I’m also getting reports from folks using that platform that it’s health routine is causing the clients to update to 1803.  Any routine that will cause workstations to check for updates will trigger the “seeker” behavior and cause 1803 to install.  Fix now released install the May 1803 update.See https://blogs.msmvps.com/bradley/2018/05/02/1803-and-issues-with-essentials/
    6. Issues with SSDs on Surface Pro devices. Specially Intel SSD 600p Series or Intel SSD Pro 6000p Series.   Known.  Microsoft has blocked the update from systems.
    7. Issues with Toshiba XG4 Series, Toshiba XG5 Series or Toshiba BG3 Series SSD drives.  Known.  Noted here and here.


  • Patch Lady – don’t go around the block

    Posted on May 3rd, 2018 at 13:01 Susan Bradley Comment on the AskWoody Lounge

    For those with certain models of Alienware machines read on for issues with 1803:

    Do not go around the block:


    Side effects include not being able to wake from sleep. Go Back to 1709 under Settings > Update & security > Recovery

    Alienware 13 R3
    Alienware 15 R3
    Alienware 15 R4
    Alienware 17 R4
    Alienware 17 R5

    Microsoft is currently blocking these models from installing the update due to a known incompatibility that may cause these devices to display a black screen after resuming from battery saver mode. For this reason, we do not recommend attempting to work around the current block to install the April 2018 Update. Microsoft is currently working on a solution that will be provided in a future Windows Update, after which these devices will be able to install the April 2018 Update.

    If you are receiving this message, you do not need to take any action at this time. There are no apps that need to be uninstalled. Windows Update will notify you when the April 2018 Update is ready for your device.

  • Patch Lady – Simplification in the GUI

    Posted on May 3rd, 2018 at 01:21 Susan Bradley Comment on the AskWoody Lounge

    In the 1803 release Microsoft made some changes in the Windows update section to make it more streamlined and simple.  Bottom line that entire section in the Pro sku where inside the GUI you could push off the Feature update up to 365 days isn’t there anymore.  Kinda.  Well at least in the GUI it’s gone.  But the good news is under the hood it’s still there.

    The streamlining means you only have pause for 7 days as a GUI option.  You can see the changes here:


    It is thankfully still fully available to be adjusted by using local group policy or registry keys.

    However it obviously isn’t quite as standalone user friendly as it used to be.  To adjust this using the local group policy editor, IF YOU HAVE THE PRO SKU and 1803 (which if you want to control updates you must have) in the search box type in gpedit.  Click to launch the local group policy editor that is offered up.  Find the Local Computer policy, then computer configuration and open up the administrative templates tab.  Find the windows components section and scroll all the way down to Windows updates.  Now find the Windows update for business folder in the right hand side of the pane and click to expand.  You’ll see the select when preview builds and feature updates are received.  Open it up.  Enable the setting and choose semi-annual channel and then you can choose to push off feature updates for up to 365 days.

    So the same deferral is still there in 1803, but not quite as easy to find the settings as 1709 if you are using a standalone Windows 10 pro sku.

  • Patch Lady – Semi annual naming is still confusing

    Posted on May 1st, 2018 at 23:01 Susan Bradley Comment on the AskWoody Lounge

    So I’ve seen several questions on the Patch Management list about the naming of the Feature releases and the confusion about what release is what.  Clearly even Microsoft is confused.  Case in point:


    On Microsoft’s own documentation they are getting the two releases confused.

    Semi-Annual targeted channel is the old Current Branch release.  It’s what 1803 – the April release is now.  It means that the feature release is just out, it’s too soon to be deemed solid for business.

    Semi-Annual channel  – just plain – is the old Current Branch for Business.  It’s when the feature release is designated to be ready for business.

    Yet in the chart above as you can see the release versions are exactly backwards.

    Microsoft changed the naming to align with what Office release naming is, but I honestly think they need to go back to the drawing board and try naming these releases again for both Windows and Office.  Clearly they are confusing even for Microsoft.  Clearly they are confusing to the Admin crowd.  Clearly they are confusing even for end users trying to figure out where they should be on what feature release.