Windows 7 Connect Issue with GP 5.2.1-9

[MacGyver]

Yes, I know it's Windows 7, but with COVID the new hardware delivery has been delayed yet again.  This is a short term issue, but it's mission critical.

The machines were connecting just fine using the previous version of GlobalProtect.  Now our vendor is forcing us to connect using 5.2.  

On later Windows 7 machines it loads and runs flawlessly.  On the existing workstations which are probably a little older, I could not get 5.2 to load.  Then I realized it was a SHA256 issue.  MS released an update for that last year.  After applying that, I can get 5.2 to load, but not connect.  It looks like at connect we do not get the:

(T6400)Debug(5090): 11/03/20 19:29:31:963 Gateway xxx.xxxxxxxx.com, response to the hip report check:

               <response status="success">

                              <hip-report-needed>yes</hip-report-needed>

                              <delay>0</delay>

               </response>

Instead, it fails.

If we cannot resolve this before Monday, we will have move hundreds of files back to an old legacy system to try and be able to open on Monday.  Our vendor has been unable to resolve the issue.  Any help would be much appreciated.

[MacGyver]

One quick update.  The PANGP Virtual Ethernet Adapter in Device Manger shows, "Windows cannot initialize the device driver for this hardware. (Code 37)"

[kinghnvn]

the same the issue. Did you fix this issue? Mac

I think we should re-install Windows OS 🙂

[MacGyver]

Yes, but sadly, not in a good way.  It required migrating 35 workstations to Windows 10.  I wish I had better news for you.  SoftPro over promised and under delivered.  Typical sales-liar approach.