1 2 Previous Next 16 Replies Latest reply on Nov 29, 2018 12:21 PM by samezrp

    Can't Install VMware Bridge Protocol After Fall Creators Update

    bmwilson74 Lurker

      Hello,

       

      I just installed Windows 10 Fall Creators Update (1709) and it removed the VMware Bridge Protocol from my physical NIC.

       

      No problem - it's easy to add back. Just go Properties of the NIC->Install->Service->VMware->VMware Bridge Protocol but the problem is it now shows the error:

       

       

      "Could not add the requested feature. The error is: Access is denied"

       

      I am running with Administrator privileges and I've always been able to do this in the past when an update has messed VMware Bridge Protocol up.

       

      Any thoughts?

       

      Thanks,

       

      Ben.

        • 1. Re: Can't Install VMware Bridge Protocol After Fall Creators Update
          MikDima Novice

          Same issue here, any help is apreciated, thanks!

          • 2. Re: Can't Install VMware Bridge Protocol After Fall Creators Update
            bmwilson74 Lurker

            Thanks for the response.

             

            I was thinking of doing a winsock reset as in 'Use network reset to reinstall network devices' at https://support.microsoft.com/en-ca/help/10741/windows-10-fix-network-connection-issues  or with the command line at http://forum.thewindowsclub.com/windows-tips-tutorials-articles/35087-how-reset-winsock-windows-10-8-7-a.html

             

            ...but I'm a bit afraid to in case I end up in worse shape than I am now!

             

            Thanks,

             

            Ben.

            • 3. Re: Can't Install VMware Bridge Protocol After Fall Creators Update
              MikDima Novice

              mh... there must be something changed in Windows Creators Fall because today I was not able to install the Cisco AnyConnect Client... both services depends on the network services/interfaces... mystery at the moment

              • 4. Re: Can't Install VMware Bridge Protocol After Fall Creators Update
                bmwilson74 Lurker

                Interesting. I have the AnyConnect client installed too. It's working though. Seems like a pattern there.

                • 5. Re: Can't Install VMware Bridge Protocol After Fall Creators Update
                  MikDima Novice

                  Digging and digging...

                   

                  I cleaned the driver from the driver store ("pnputil.exe -d Oem26.inf" in my case), then I reinstalled from the INF file (netbridge.inf), this is the content of the setupapi.dev.log:

                   

                   

                  ==========================================================

                  >>>  [SetupCopyOEMInf - c:\program files (x86)\vmware\vmware player\netbridge.inf]

                  >>>  Section start 2017/12/05 23:36:42.398

                        cmd: C:\WINDOWS\system32\DllHost.exe /Processid:{7007ACD1-3202-11D1-AAD2-00805FC1270E}

                       inf: Copy style: 0x00000000

                       sto: {Setup Import Driver Package: c:\program files (x86)\vmware\vmware player\netbridge.inf} 23:36:42.400

                       inf:      Provider: VMware, Inc.

                       inf:      Class GUID: {4D36E974-E325-11CE-BFC1-08002BE10318}

                       inf:      Driver Version: 12/09/2016,4.2.8.0

                       inf:      Catalog File: vmnetbridge.cat

                       sto:      {Copy Driver Package: c:\program files (x86)\vmware\vmware player\netbridge.inf} 23:36:42.404

                       sto:           Driver Package = c:\program files (x86)\vmware\vmware player\netbridge.inf

                       sto:           Flags          = 0x00000007

                       sto:           Destination    = C:\Users\Michele DM\AppData\Local\Temp\{fba5ae21-5da1-f94f-bc81-f4f4a85ded46}

                       sto:           Copying driver package files to 'C:\Users\Michele DM\AppData\Local\Temp\{fba5ae21-5da1-f94f-bc81-f4f4a85ded46}'.

                       flq:           Copying 'c:\program files (x86)\vmware\vmware player\vmnetbridge.cat' to 'C:\Users\Michele DM\AppData\Local\Temp\{fba5ae21-5da1-f94f-bc81-f4f4a85ded46}\vmnetbridge.cat'.

                       flq:           Copying 'c:\program files (x86)\vmware\vmware player\vmnetbridge.dll' to 'C:\Users\Michele DM\AppData\Local\Temp\{fba5ae21-5da1-f94f-bc81-f4f4a85ded46}\vmnetbridge.dll'.

                       flq:           Copying 'c:\program files (x86)\vmware\vmware player\vmnetbridge.sys' to 'C:\Users\Michele DM\AppData\Local\Temp\{fba5ae21-5da1-f94f-bc81-f4f4a85ded46}\vmnetbridge.sys'.

                       flq:           Copying 'c:\program files (x86)\vmware\vmware player\netbridge.inf' to 'C:\Users\Michele DM\AppData\Local\Temp\{fba5ae21-5da1-f94f-bc81-f4f4a85ded46}\netbridge.inf'.

                       flq:           Copying 'c:\program files (x86)\vmware\vmware player\vmnet.sys' to 'C:\Users\Michele DM\AppData\Local\Temp\{fba5ae21-5da1-f94f-bc81-f4f4a85ded46}\vmnet.sys'.

                       sto:      {Copy Driver Package: exit(0x00000000)} 23:36:42.450

                       pol:      {Driver package policy check} 23:36:42.455

                       pol:      {Driver package policy check - exit(0x00000000)} 23:36:42.456

                       sto:      {Stage Driver Package: C:\Users\Michele DM\AppData\Local\Temp\{fba5ae21-5da1-f94f-bc81-f4f4a85ded46}\netbridge.inf} 23:36:42.456

                       inf:           {Query Configurability: C:\Users\Michele DM\AppData\Local\Temp\{fba5ae21-5da1-f94f-bc81-f4f4a85ded46}\netbridge.inf} 23:36:42.460

                       inf:                Driver package 'netbridge.inf' is configurable.

                       inf:           {Query Configurability: exit(0x00000000)} 23:36:42.462

                       flq:           Copying 'C:\Users\Michele DM\AppData\Local\Temp\{fba5ae21-5da1-f94f-bc81-f4f4a85ded46}\vmnetbridge.cat' to 'C:\WINDOWS\System32\DriverStore\Temp\{1af02098-fc1c-3941-957a-252094e7eb69}\vmnetbridge.cat'.

                       flq:           Copying 'C:\Users\Michele DM\AppData\Local\Temp\{fba5ae21-5da1-f94f-bc81-f4f4a85ded46}\vmnetbridge.dll' to 'C:\WINDOWS\System32\DriverStore\Temp\{1af02098-fc1c-3941-957a-252094e7eb69}\vmnetbridge.dll'.

                       flq:           Copying 'C:\Users\Michele DM\AppData\Local\Temp\{fba5ae21-5da1-f94f-bc81-f4f4a85ded46}\vmnetbridge.sys' to 'C:\WINDOWS\System32\DriverStore\Temp\{1af02098-fc1c-3941-957a-252094e7eb69}\vmnetbridge.sys'.

                       flq:           Copying 'C:\Users\Michele DM\AppData\Local\Temp\{fba5ae21-5da1-f94f-bc81-f4f4a85ded46}\netbridge.inf' to 'C:\WINDOWS\System32\DriverStore\Temp\{1af02098-fc1c-3941-957a-252094e7eb69}\netbridge.inf'.

                       flq:           Copying 'C:\Users\Michele DM\AppData\Local\Temp\{fba5ae21-5da1-f94f-bc81-f4f4a85ded46}\vmnet.sys' to 'C:\WINDOWS\System32\DriverStore\Temp\{1af02098-fc1c-3941-957a-252094e7eb69}\vmnet.sys'.

                       sto:           {DRIVERSTORE IMPORT VALIDATE} 23:36:42.556

                       sig:                {_VERIFY_FILE_SIGNATURE} 23:36:42.577

                       sig:                     Key      = netbridge.inf

                       sig:                     FilePath = C:\WINDOWS\System32\DriverStore\Temp\{1af02098-fc1c-3941-957a-252094e7eb69}\netbridge.inf

                       sig:                     Catalog  = C:\WINDOWS\System32\DriverStore\Temp\{1af02098-fc1c-3941-957a-252094e7eb69}\vmnetbridge.cat

                       sig:                     Success: File is signed in catalog.

                       sig:                {_VERIFY_FILE_SIGNATURE exit(0x00000000)} 23:36:42.599

                       sto:           {DRIVERSTORE IMPORT VALIDATE: exit(0x00000000)} 23:36:42.605

                       sig:           Signer Score = 0x0D000005

                       sig:           Signer Name  = Microsoft Windows Hardware Compatibility Publisher

                       sto:           {DRIVERSTORE IMPORT BEGIN} 23:36:42.613

                       sto:           {DRIVERSTORE IMPORT BEGIN: exit(0x00000000)} 23:36:42.614

                       cpy:           {Copy Directory: C:\WINDOWS\System32\DriverStore\Temp\{1af02098-fc1c-3941-957a-252094e7eb69}} 23:36:42.614

                       cpy:                Target Path = C:\WINDOWS\System32\DriverStore\FileRepository\netbridge.inf_amd64_d8dc5ede97ee5034

                       cpy:           {Copy Directory: exit(0x00000000)} 23:36:42.618

                       idb:           {Register Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\netbridge.inf_amd64_d8dc5ede97ee5034\netbridge.inf} 23:36:42.619

                       idb:                Created driver package object 'netbridge.inf_amd64_d8dc5ede97ee5034' in DRIVERS database node.

                       idb:                Created driver INF file object 'oem26.inf' in DRIVERS database node.

                       idb:                Registered driver package 'netbridge.inf_amd64_d8dc5ede97ee5034' with 'oem26.inf'.

                       idb:           {Register Driver Package: exit(0x00000000)} 23:36:42.621

                       idb:           {Publish Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\netbridge.inf_amd64_d8dc5ede97ee5034\netbridge.inf} 23:36:42.622

                       idb:                Activating driver package 'netbridge.inf_amd64_d8dc5ede97ee5034'.

                       cpy:                Published 'netbridge.inf_amd64_d8dc5ede97ee5034\netbridge.inf' to 'oem26.inf'.

                       idb:                Indexed 2 device IDs for 'netbridge.inf_amd64_d8dc5ede97ee5034'.

                       sto:                Flushed driver database node 'DRIVERS'. Time = 0 ms

                       sto:                Flushed driver database node 'SYSTEM'. Time = 0 ms

                       idb:           {Publish Driver Package: exit(0x00000000)} 23:36:42.631

                       sto:           {DRIVERSTORE IMPORT END} 23:36:42.632

                       dvi:                Flushed all driver package files to disk. Time = 0 ms

                       sig:                Installed catalog 'vmnetbridge.cat' as 'oem26.cat'.

                       sto:           {DRIVERSTORE IMPORT END: exit(0x00000000)} 23:36:42.641

                       sto:      {Stage Driver Package: exit(0x00000000)} 23:36:42.643

                  !    dvi:      Unable to mark devices that match new INF - (00000490)!

                       sto: {Setup Import Driver Package - exit (0x00000000)} 23:36:42.655

                       inf: Driver Store Path: C:\WINDOWS\System32\DriverStore\FileRepository\netbridge.inf_amd64_d8dc5ede97ee5034\netbridge.inf

                       inf: Published Inf Path: C:\WINDOWS\INF\oem26.inf

                  <<<  Section end 2017/12/05 23:36:42.657

                  ==========================================================

                   

                  But still I did not find anything to solve this issue...

                  • 6. Re: Can't Install VMware Bridge Protocol After Fall Creators Update
                    dhcinc Novice

                    I am seeing the same thing here. I have re-installed the Workstation 12, tried Workstation 14, updated the network drivers and nothing allows me to install the VMware Bridge Protocol service. Also running the VMware Virtual Network Editor and selecting 'Restore Defaults' isn't working either. I get VMnet1 and VMnet8 but no VMnet0. I need to resolve this quickly as I have a number of development VM images that need to talk on the networks.

                     

                    I tried NAT as well but it gets stuck at 'Identifying Network'.

                    • 7. Re: Can't Install VMware Bridge Protocol After Fall Creators Update
                      bmwilson74 Lurker

                      I found at least the NAT worked ok for me thankfully. Have you checked that all the VMware windows services for NAT are started successfully?

                       

                      Maybe try the winsock reset mentioned above. I've not been brave enough to try it but it sounds like it might be worth the risk.

                      • 8. Re: Can't Install VMware Bridge Protocol After Fall Creators Update
                        MikDima Novice

                        Well, I think something has changed in creators fall update about installing a network driver, and we must wait for a new release of VMWare to be compliant...

                        • 9. Re: Can't Install VMware Bridge Protocol After Fall Creators Update
                          BenSuckling Lurker

                          I'm not sure about it being only a Win10 issue - I'm having the same problem after upgrading from WS 12.5.6 -> 12.5.8 on Windows 7 x64...

                          • 10. Re: Can't Install VMware Bridge Protocol After Fall Creators Update
                            MikDima Novice

                            Ok, I found the issue, I write to update you all.

                             

                            In my case was the "CheckPoint VPN Client" that caused the issue.

                            I uninstalled Checkpoint, the "VMware Bridge Protcol" just installed like a charm and everything was working.

                             

                            The version of CheckPoint VPN was E80.70, now I try to update to E80.72 and see if the problem is still there.

                            • 11. Re: Can't Install VMware Bridge Protocol After Fall Creators Update
                              reachbesal1 Lurker

                              Thanks for the update MikDima, did you have issues after installing version 80.72 ? if yes then have you been able to resolve it?

                              • 12. Re: Can't Install VMware Bridge Protocol After Fall Creators Update
                                MikDima Novice

                                Yes, with the version 80.72 the problem seems to be resolved.

                                 

                                Just: I have a doubt about the path I followed. I uninstalled the previous version of CheckPoint, resolved an issue with my LAN Card driver (went totally unusable updating the driver), resolved the issue with VMWare, then I reinstalled CheckPoint. So I am not 100% sure that everything will work with CheckPoint 80.72 already installed... but this path works for sure!

                                Everything now works and it is stable.

                                • 13. Re: Can't Install VMware Bridge Protocol After Fall Creators Update
                                  reachbesal1 Lurker

                                  hank you for your quick reply, have you tried installing any any software that requires a NIC after upgrading to 80.72 to see if the issue still persists

                                  • 14. Re: Can't Install VMware Bridge Protocol After Fall Creators Update
                                    MacFred Lurker

                                    Its a rights problem in Windows 10 the local administrator

                                    1. Administrator to "Network Configuration Operators"

                                    2. And start Virtual Network Editor" and "Restore Defaults"

                                     

                                    Just found this problem on my computers that the "local administrator" dosen't have the rights to add a service to the network connection!

                                    The same issue on 1607 1703 and 1709.

                                     

                                    Good Luck

                                     

                                    Fredrik

                                    1 2 Previous Next