On Friday June 8th, Microsoft has started to block offering up Windows 1803 Update to our customers as an automatic update (until the resolution is properly resolved).
If the following registry key is found on a Win10 machine, Microsoft will not offer up Windows 1803 as an automatic update.
However, it will not block a user / admin who “checks for updates” from updating if they choose.
Bentley and Microsoft have identified the root cause of the issue and are actually working on a solution
Bentley understands the impact and urgency of this issue (Please see the following post from the MicroStation Forum)
[Note for developers/programmers only]
Known Issue – Universal CRT ctype functions can fail with EOF input (Windows 10 1803 SDK (17134), April 2018 release.)
This same update has also caused crashes when using AecoSim Building Designer and InterPlot Organizer 10.00.00.xx, see the following wikis:
Microsoft has started to block offering up Windows 1803 Update to our customers as an automatic update (until the resolution is properly resolved).
Please continue to advise our users not to update until this issue is resolved.
Microsoft has a fix in the works and will be available shortly
Microsoft pushed a fix to the Windows 10 Insiders Fast Ring (Build 17692) on Thursday, June 14. Since no major regressions were found by Windows Insiders, the fix was approved and checked in yesterday and is currently scheduled to go out to everyone with next security updates on Tuesday, July 10th.
Note: Bentley does NOT recommend becoming part of the Windows Insiders program, but rather we suggest you wait until July 10th for the fix..
While this fix is now scheduled for release earlier that the originally estimated August time frame, we understand how important resolving the issue is. Bentley is continuing to work with Microsoft advocating on your behalf to get a public fix sooner.
Bentley is aware of at least three other major ISVs affected by this problem as well, so we are not alone in our fight.
Last week, Bentley worked closely with Microsoft to test the July 10th security updates and found that Microsoft did not commit all the necessary pieces to fix our problem. Thus, tomorrow's security updates will NOT resolve this issue. We tried desperately to escalate the case and get the security patch rebuilt, but Microsoft management declined our request due to their inability to provide enough security assurance testing before it gets released out to the world.
Root cause of why our fix wasn't committed was identified and has been resolved and the proper fix is currently scheduled to go out to everyone with next set of security updates during the week of July 23rd. We will continue to work daily with Microsoft until this issue gets resolved.
Other Language Sources