Windows 10 v 1803 Breaks Hydraflow

[Anonymous]

Just a heads up - the April 2018 Update will cause Hydraflow pond outflows to increase every time "Compute" is pressed. Going back to Windows 10 v 1709 resolved the issue.

[Anonymous]

I just noticed this as well.  Very frustrating.

[ChrisRS]

If you have not submitted a support case, it would be good to do so. You can not count on the Civil 3D team monitoring this forum and reacting.

[ralphsanchezATX]

Which version of Civil 3D / Hydraflow did you see this happen with?

[Anonymous]

Hydraflow v 10.514 (C3D 2016) & v 12 (C3D 2018 & 2019)

I've submitted a ticket to Autodesk - I would suggest anyone else experiencing this to do the same.

[Anonymous]

I have experienced this as well using Civil3D 2018 - Hydraflow. Very frustrating.

[Anonymous]

Please be sure to send a ticket in with AutoDesk

[Mike_Hurtado]

Thank you for bringing this to our attention! It's currently being looked into by our development team.

[Anonymous]

Having the same problem...

I am trying to design a simple detention basin and in the pond tools it keeps telling me "nothing to plot" and "insufficient pond data". This is the first time I have used Hydraflow since the new Windows 10 update version 1803.

[Anonymous]

Are there any updates on the progress of finding a solution? 

[jporter]

We have a client who is experiencing the same issue.  Since it is being looked at by Autodesk at this time (per @Mike_Hurtado above), I recommend taking the project forward to 2019 or backward to an earlier version.  Since I'm on a Windows 8 system and not a Windows 10 system I can't test.  I'll let you know the results once I have them unless one of you wants to be so kind to test yourselves.  If you need to know the procedure to take a Civil 3D drawing back to earlier versions the process is here:  https://www.asti.com/civil-3d-2017-not-so-easily-compatible-with-older-software/

[Anonymous]

I've already tested on 2019 and 2016 versions of Hydraflow. Both are experiencing the same problem. Hydraflow v 10.514 (C3D 2016) & v 12 (C3D 2018 & 2019) both do not work with Win10 v1803. In order to resolve the issue, you must go back to Win 10 fall update (Win 10 v1709). Going back to an earlier version of AutoCAD does not work.

[jporter]

And how long did you have the update installed prior to you backing out of it?  I only ask because I was informed by my client that this cannot he couldn't back out of the Windows update after it has been installed for 10 days.  I've not heard of that, but then again, I don't have a Windows 10 system to test.  Should this not be the procedure:  http://www.thewindowsclub.com/rollback-uninstall-windows-10-creators-update.  

[Anonymous]

Fortunately, I was able to back out because the update was only a day old. What you've linked to is the correct procedure to go back to 1709. However, we had another engineer in our office whose computer updated and was not able to back out of it even though it had been less than 10 days due to a corrupted restore point. We've paused Windows Update across our computers in the office as a result of the issues with the v1803. I recommend all engineers who use Hydraflow to pause updates until Autodesk or Microsoft resolve the issue. 

[jporter]

Thanks, @Anonymous.  I was hoping that maybe backing out back to the 1709 update may resolve the issue, but it sounds like that 1803 update hijacks everything.  Here's hoping Autodesk or Microsoft will come up with a solution soon.  

[Anonymous]

This was the case for me as well. Past 10 days since windows update and unable to roll back the Windows update. All the work-around suggestions were not possible. Here is hoping Autodesk/Windows provide a fix asap! 

[gparadoski]

WORK HARDER, FASTER, LONGER TO FIX THIS!!!!!  We certainly do.

[gparadoski]

It keeps increasing the number of Outlet barrels each time you click compute.  Just shut off that option for now and push out a hotfix so we can keep working while you fix it.  Thanks!

[wfberry]

Well, I have two thoughts on this Microsoft/Autodesk problem, it has been around for 2 months.

1.  Microsoft doesn't care.

2.  Autodesk cannot figure it out.

Bill

[jporter]

As expected, we now have many clients experiencing this issue.  One recently had a Microsoft technician pay a visit in a failed attempt to try to resolve this from Microsoft's end.  He was informed that Microsoft is aware of several software that has issues since this new update.  According to the client, Microsoft is hoping for some patches.  But, honestly, in my opinion they don't know how Autodesk (or other non-Microsoft) software works or is programmed.  Even if Microsoft should fix this on there end will it break something else?  I don't expect Microsoft to have a resolution to this.  I was actually hoping they could simply provide a way to uninstall the update after the 10-day window has passed.  That would probably be the best they can do.  

As far as Autodesk goes, they are only responding to an update that was released.  Remember, they get the Microsoft updates the same we we all do.  I'm just hoping the programmers find a resolution real soon.