Forum Discussion

Zain Khan's avatar
Zain Khan
Copper Contributor
Aug 02, 2017

Feature Update to Windows 10 Enterpise 1703 cause IE 11 to become corrupt

Hi,   I just did a Feature update to Windows 10 Enterprise 1703 Creators update via SCCM using servicing on my custom Win10 Enterprise 1607 image.  This caused Internet Explorer 11 to become corrup...
Zain Khan's avatar
Zain Khan
Copper Contributor
Oct 26, 2017

Thanks Steve,

 

We were able to finally figure out what was causing the issue after feature update.  We have a 3rd party application named Beyond Trust Power Broker Desktop Client installed in our Core Applications which helps with program right elevation via GPO.  We found that the driver was Not compatible with Win10 v1703 and that upgrading the Power Broker client resolved the issue.  I thought I would share this to help anyone else having the issue.

 

Regards,

Zain

William Kurz's avatar
William Kurz
Copper Contributor
Oct 26, 2017

Zain,

 

I'm so very, very grateful for your post. I cannot thank you enough. You've just saved me untold hours of troubleshooting.

 

I happened to be working through the steps today for our company to upgrade from 1607 to 1709 (by way of 1703) and came across the exact IE11 issue you originally described. Earlier today, when I started searching the Internet for answers, I found your 21 minute old (at that time) post that mentioned PowerBroker caused this issue for you. We also use PowerBroker, and ours is also an older version. I just finished testing removal of PowerBroker pre-upgrade and Viola!... the problem is resolved. IE11 now works normally post-upgrade.

 

FYI for anyone else that finds this... I found that trying to remove PowerBroker post-upgrade (as opposed to pre-upgrade) was not possible. I assume that this was for the same reasons that IE11 won't work properly.

 

- Bill

  • Zain Khan's avatar
    Zain Khan
    Copper Contributor
    Oct 27, 2017
    Your Welcome, I'm glad my post was able to help as I never post to forums but I guess I was irritated enough lol :). I wish I was able to share the solution sooner, but ended up getting busy with some imaging updates.

    This did leave me scratching my head for some time, eventually a Microsoft premier case was opened since we had some user's machine get automatically upgraded to 1703 via windows update. We were able to find that the driver faulting was associated to PowerBroker and disabling the driver from starting in the registry resolved the issue. After some researching we found the older PowerBroker version was not 1703 compatible and upgrading it to PowerBroker v7.3.0.30 resolved the issue.

    One thing to note, I found that the latest PB version caused the same issue on an old machine with on of the first Windows 10 releases prior to 1511. Just wanted to mention it incase you do still have older Win10 versions in your environment.
    • Michael Ferstl's avatar
      Michael Ferstl
      Copper Contributor
      Nov 07, 2017

       

      Hi,

      We have the same issue, i just didn't figure out which driver to disable in the registry?

      Could you share the registry key with us?

      thanks a lot

      michael

      • Zain Khan's avatar
        Zain Khan
        Copper Contributor
        Dec 19, 2017

        Sorry for the delayed response, I guess I missed the notification.  Not sure if you still need the info, but sharing in case it helps others.  Below the where you disable the privman driver from starting, just change the "Start" value to 4 to disable.

         

        [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\privman]
        "Start"=dword:00000004
        "DisplayName"="privman"
        "Description"="privman mini-filter driver"