** HOTFIX RELEASED for Windows 10 April Release build 1803 issues **

[SethHall]

Hello all-

We have been evaluating issues caused by the latest update to Windows 10 build 1803. If you haven't updated, please hold off for the time being. You can do so by following these instructions: https://support.microsoft.com/en-us/help/4026834/windows-10-defer-upgrades

We will update this thread with any further information as it is available.

[JasonArtley]

Does this upgrade affect Infraworks only or other Autodesk products as well?

[SethHall]

@JasonArtley

I am not sure, are you seeing some issues with another product?

[JasonArtley]

No not yet, but I want to be prepared just in case. 

[SethHall]

New Autodesk Knowledge Network article put together by @AlmasSuljevic

https://knowledge.autodesk.com/support/infraworks/troubleshooting/caas/sfdcarticles/sfdcarticles/Inf...

I tested the steps to roll back versions as stated in the article and InfraWorks install remained intact. The hang was not present in all known situations once I was not on build 1803.

[Anonymous]

Hope you fix this soon, I can not go back to the old win because I deleted the window.old file

[Anonymous]

Recent model created through Model Builder won't open.

[ChrisRS]

It seem like this post should by pinned.

There are Civil 3D users that use Infraworks less frequently and may not browse this forum often. It may be prudent to post/pin in the Civil 3d Forum as well. 

[TomislavGolubovic]

I'm on 1803 with OS build 17134.1 and IW 2019 (19.0.65.0) works for me?

[SethHall]

@Anonymous

I am not sure the two issues are related. Does this happen to all models created form Model Builder, or just one? Are you on 1803 build of Windows 10?

[Anonymous]

Hi Seth,
My mistake. I assumed that our IT updated me to Windows 10. Our IT updated a certificate on my system and now I can open the Model. Not related to Windows 10.

[ToddRogers-WPM]

@SethHall Well, we started having issues yesterday. First, one person found they could not plot to PDF, "Exiting Now" error. Then, one other person could not print to PDF because of crash. By the end of the day yesterday, about 6 people had this same issue. We found that you could EXPORTPDF without issue.

BTW, this is Civil 3D.

[SethHall]

Hi @ToddRogers-WPM

Did you report this to the C3D/AutoCAD team? Is everyone running 1803?

Thanks!

[ToddRogers-WPM]

I have not. I will check that and find out for you and let you know in the morning.  I will also report that to them as soon I find out the build.

[ChrisRS]

@SethHall

---

@SethHallwrote:

Hi @ToddRogers-WPM

Did you report this to the C3D/AutoCAD team? Is everyone running 1803?

Thanks!

---

Seth, I ask this with as due respect, but how does a user report a problem to the C3D/AutoCAD team?

We can submit a support case, but in my experience, the Autodesk support technicians do not seem to seem to be very closely linked to the teams. I have yet to hear back on any of several support issues that have been escalated to "the team." 

I am glad the you are out in front of this issue. I am particularly glad to see that this post was "pinned."

@ToddRogers-WPMis apparently having problems in C3D. There is a post in C3D titled "Windows 10 v 1803 breaks Hydraflow". If there are suspected problems with 1803 for other Autodesk programs, I think warnings should be posted/pinned in the appropriate forums. I do not think I am the person to do that. 

[SethHall]

Hi @ChrisRS

Thanks for reaching out. Coming from a Support role years ago I understand the importance of bridging the gap between customers and the development teams. That is why you will see me posting here frequently, and helping out when I am able to. I like to get ahead of issues, and also observe how our hard work is received by customers, bringing up any issues to my team, as well as other teams within our group.

I am sorry to hear that some of your requests or issues have not been addressed, but we (development teams) honestly try to prioritize and provide the best experience possible. @ToddRogers-WPM and I go way back, so my response to him may have been a little casual, as I know he will log these issues with AutoCAD and/or Civil 3D support teams where applicable. Personally I have not heard of any specific issues with other products, other than the ones you and Todd brought up, but I will follow up with the Civil 3D team today to see if a similar post needs to be pinned on other forums.

As for this issue, we have been in contact with Microsoft and are hoping to have some sort of resolution shortly.

[ToddRogers-WPM]

Well I have some sad news for myself this morning. I checked the machines and IT never rolled out the 1803 update. The machines that are having this issue are on build 1703 So, I'm thinking this may not have ANYTHING to do with the software per se. I do know we are running Panzura, and IT is checking on this.

I'm going to hold off on creating a case with you guys untjl we can eliminate some of the other issues first.

Thanks as always @SethHall, and I will keep ya'll posted!

[SethHall]

Just to give everyone an update on this, we have a Hotfix in the works. Stay tuned for any updates. Thanks again for your patience.

[sergiumedrea]

Hi there,

After windows update Infraworks is not opening models. It gives an error and then shuts down.

Civil 3D and Revit are opening, but in civil 3D i can not see the crosshair or the viewcube unless i disable the Graphics Performance, same with Revit. More so, the start tab in civil 3D is not visible.

I tried reinstalling civil 3D, but no luck. I tried uninstalling / reinstalling nVidia driver, but no luck.

Actually when i uninstalled nvidia driver, civil 3D would work just fine. Haven't tested Infraworks though, because windows installed an older version of nvidia driver automatically.

My guess is that this it is an nvidia driver problem, because if i open google earth with nvidia driver it shows a blank screen, if i open it using integrated graphic card (intel) it works just fine.

Hope this helps.

Regards.

[Matt__W]

@SethHall On a possibly related note, since the 1803 update I've lost all functionality of InfraWorks. I'm apparently now in Trial Mode. The tools showed up after the initial launch of InfraWorks (post-1803 update) as I decided to test it out. The older properties palette (not The Stack) came up fine and appeared to be working however when I attempted to place a component road, that's when it froze for me - guess it doesn't like The Stack, huh? After forcing InfraWorks to shut down and re-opening it, that's when all of the tools were lost. My Autodesk account page shows my Expert Elite license of InfraWorks is valid until Jan 4, 2020. I haven't attempted an uninstall/reinstall of the application yet. Been hoping there's something on the back end that needs to get caught up or refreshed. I'm in no big rush as this is a test situation but.... it would be nice to know if the two are related (1803 and loss of functionality). It's important to note that I've since rolled back to 1709 and the tools are still missing.