Anuncios

The Autodesk Community Forums has a new look. Read more about what's changed on the Community Announcements board.

JamesMaeding
en respuesta a: JamesMaeding

so an update on the issue.

Autodesk support told me they expect us to talk to them to figure out what to do on a particular environment.

That would be ok for the first few rounds of when the issue was discovered, but we know exactly what is causing the issue, and I believe how to fix it.

 

The idea of uninstalling .net 4.6, or hacking the reg to trick windows into not seeing it, is way out of the range of reality for people supporting more than say 10 users.

The only real solution seems to be editing the .msi files using orca, and that is very easy to do.

I did that for our IDSP and it worked perfect (win 7 64 bit and win 8) I did not try on 10 yet.

 

But is anyone finding that does not always work?

 

One issue I am seeing is a repair install seems to hang on the 4.6 issue, and that implies I did not fix the msi's in the folder where the install was done, or that there is another mechanism involved. working on that.

 

We need to hound Autodesk on this, to fix its install media and re-release it. Tons of places are on 2015, and we get that it would have been hard to foresee the issue.

To ignore it is a new level of customer whipping though.


internal protected virtual unsafe Human() : mostlyHarmless
I'm just here for the Shelties