Jeremy Wright wrote:
UPDATE:
We worked over the weekend with Microsoft on this issue and found the root cause was the security patch, BUT we discovered a fix we can do on our end.
The fix has been tested and the QFE team has begun the process of porting the fix back to the relevant versions.
We're also publishing a KB article with all known details on the issue and all of the known workarounds for those that need fixes right now.
I'll update the thread with the KB article as soon as it is copy edited and posted, in the meantime here's the draft of the workarounds section:
Workarounds:
There are several workarounds that can be used until general patches are available. Choose one of the following strategies:
- Switch the character-marker based symbols to use simple markers instead, and republish the map. Simple markers are not affected by this issue as they do not use the affected Windows GDI method to be published.
Sorry, but I'm quite new to GIS, how is this step accomplished?
- Republish the map from ArcGIS Pro instead of publishing from ArcGIS Desktop. This can be done by importing the MXD into Pro and sharing via a portal connection or to server directly. ArcGIS Pro publishing uses a different code path that’s not dependent on the faulting GDI function.
Publishing from ArcGIS Pro did not resolve the issue.
- Roll back the security updates temporarily on either client or server machines:
- If publishing a map or feature service to ArcGIS Server directly or ArcGIS Enterprise:
- The machine on which ArcGIS Server is installed must be rolled back to before the June security patches for Microsoft Windows (KB4503286 or KB4503276) and opted out of updates until a resolution is available, and the affected services must be restarted.
- If publishing a hosted service to ArcGIS Enterprise or ArcGIS Online:
- The machine on which ArcGIS Desktop is installed must be rolled back to before the June security patches for Microsoft Windows (KB4503286 or KB4503276) and opted out of updates until a resolution is available, and then the affected services must be republished from the rolled-back machine.
You might add that you will need to manually turn off windows update on windows 10 or else it will automatically update after you roll it back.
Thanks for the update. I have commented on my experiences above in italics. Only one solution has worked for me thus far. I'm not updating my pc and I'm waiting to set up a new pc until this issue is fixed.