HTTPS PAC file not working in IE/Edge after Windows Update
- Article Number: 000017535
- Products: Forcepoint One Endpoint, Forcepoint Web Security Cloud, Forcepoint Web Security Endpoint Cloud
- Version: 8.5, 20, 19, 18
- Last Published Date: June 30, 2020
Problem Description
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. |
Resolution
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:
Windows 10 version 1903
Version: OS Build 18362.295 (KB4512508) Release Date: August 13, 2019 August 13, 2019—KB4512508 (OS Build 18362.295) Windows 10 version 1803
Version: OS Build 17134.950 (KB4512501) Release Date: August 13, 2019 August 13, 2019—KB4512501 (OS Build 17134.950) Keywords: windows update; endpoint; pcep; proxy connect; pac; https; edge; internet explorer; KB4512508; KB4512501; 1903; 1803; end user; browser; f1e |
Article Feedback
Want 24/7 Tech Support?
Learn more