MicroStation CONNECT Edition Update 8 stopped working when Windows 10 Spring Creators Update was installed. Someone else happened to him?
Hi everybody how are you. Something new under the sun ?Does someone know if Bentley has done or is doing something to solve the problem? It seems that microsoft will not do anything until the next version of the S.O.
Bentley has been working very closely with Microsoft on this issue. We understand the impact and urgency of this issue on your business. Bentley colleagues are also feeling your pain as well. We are continuously updating Microsoft with how this issue is affecting Bentley's business, as well as our third party developers.
Unfortunately, the root cause is in the Windows Runtime (see Known Issue – Universal CRT ctype functions can fail with EOF input (Windows 10 1803 SDK (17134), April 2018 release.)) and Bentley is working with MIcrosoft to ensure a proper Microsoft fix with no regressions or new issues.
Internally, we have also tried to workaround this issue ourselves and put out our own patch, but this issue affects such low level code that it would be nearly impossible for Bentley to implement in a reasonable amount of time.
Googling 1803 issues shows this issue impacts other ISVs (we are not alone),. In fact, any C++ based product, using the latest runtimes, may be impacted.
Unfortunately, at this time, Microsoft has not given us any specific dates of when we can expect a fix. IMO, they cannot wait until the next version of the OS to resolve this due to the magnitude of the issue.
As soon as we get more information, we will share.
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.
Please be advised not to update your Windows 10 until this issue is resolved.
Microsoft has a fix in the works and will be available shortly.
thank you very much !!
I wanted to give everyone a Quick Update on where we stand with this issue.
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.
Again, as we get more definitive information, we will share.
Hi TomThank you for your update. Nice to know that there is finally a solution to this problem. As far as I understand it, only Windows has to be updated to get MicroStation CONNECT to run again? ...no Bentley update or reinstall of CONNECT programs?With regardsAnders
Anders W said:As far as I understand it, only Windows has to be updated to get MicroStation CONNECT to run again? ...no Bentley update or reinstall of CONNECT programs?
In my opinion there will be no further action required, because MicroStation itself "only" calls Win API function, that is corrupted in April Update. When it will be repaired, MicroStation should runs fine again ;-)
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Yes, Jan's answer is correct. Connect Edition products will return to normal as soon as Windows ucrtbase.dll gets updated by Microsoft. Bentley has verified the behavior is corrected in Windows 10 Insiders Build 17692,
I test in 17704, the crash is still there.
will have to wait for the release of the final version