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.
Regards.
All,
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.
-- Tom
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
regards
I am using the same compilation (17704.rs_prerelease.180623-1611) and it does not give me problems, it works perfectly.
Last week, we 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.
We are extremely frustrated with Microsoft as we know how this impacts your business as well as ours internally.
As we get more definitive information, we will continue to share.
--Tom
thanks Tom
/pt
This is already extending too much, we can not have our operating systems updated by this error. We will arm ourselves with patience. :( :(
Regards
Hi Tom,
Is there an other update of Microstation Connect Edition I can use which is working well under Windows 10 update 1803?
Regards,