After an upgrade on Windows 10 1903 build update, browsing via Internet Explorer or Edge has stopped working.

Once the system is updated, the browser fails to parse the PAC file on HTTPS and returns no Proxy. Upon checking the Blackspider Query page, the tool says Forcepoint is not in use:
 
Essentially the browser does not acknowledge that there is a proxy in use or even possibly a PAC file, the PAC file is ignored.

This issue is related to a Microsoft update to Windows 10. Microsoft has introduced a possible bug by introducing a new flag for revocation check on PAC files over TLS.

Microsoft is aware of the issue. See IE and Edge ignore PAC (proxy auto config) file (comment from July 1, 2019).
Forcepoint recommends to contact the Microsoft team, referencing the above link, and ask to monitor/track the issue.

At present there are no known workarounds for HTTPS PAC files. 

For other workarounds:

• Forcepoint does not recommend reverting or uninstalling Microsoft updates. 
• Change back to using the HTTP PAC file.
  1. Login to Cloud portal.
  2. Navigate to Web > Policy.
  3. Click on the policy you wish to disable HTTPS PAC files.
     • This feature is policy specific and can be enabled or disabled for each policy.
  4. Navigate to Endpoint > Endpoint PAC Control.
  5. Uncheck Retrieve PAC file over HTTPS.
  6. Repeat these steps for each policy to ensure HTTPS PAC files have been disabled.

The issue appears related to the following KBs published by Microsoft:
 



Keywords:
windows update; endpoint; pcep; proxy connect; pac; https; edge; internet explorer; KB4512508; KB4512501; 1903; 1803; end user; browser; f1e