Why are Max service pack installations so SLOW?

[senorpablo]

Installing Max 2017 service pack 3. It's going on an hour now, "Gathering required information...". 

I can't fathom why it takes longer to install a 145mb service pack, than to install Windows from scratch.

[Alfred.DeFlaminis]

Hello @senorpablo,

It is pretty slow, my understanding is that it's because of .Net and C++ library installations.  

Best Regards,

[Alfred.DeFlaminis · Accepted solution]

Hello @senorpablo,

I wanted to follow up with a link from the MS site about slow .Net installations which includes some explanations why things can take so long.  I agree it does take a long time sometimes.  

Best Regards,

[Anonymous]

Then... maybe not use .NET? Use a stand-alone installer, use WinRAR sfx, anything but 45 minute updates! Your software is used in production environments, where time is money. Sometimes these downtimes are frowned upon. I mean, come on... a 250 MB file takes as long or even LONGER than if you were to install the entire base program from scratch. Jesus...

"Gathering required information..." WHAT INFORMATION? Let me point you to the install directory and have at it! What kind of information are you gathering? What kind of information are you even EXPECTING? I'll gladly provide them in a GUI or something if it means just extracting 250 MB over the install dir.

Come on... You gotta have some smart programmers at Autodesk. Stop using that .NET crap. Use C# or C++ and code your own installer that uses public compression libs under GPL, or purchase a license from one of the numerous install deployment programs that are out there.

[dgorsman]

I think you're missing a few things.

Updating the dotNET Framework isn't (only) about the installer.  It's also about the program being updated.  If the Framework isn't updated, then the updated program cannot run.

I should also point out that C#, and to a great extent, C++ *IS* dotNET.  Its used like Legos to build programs quickly.  If the developers had to build their own framework from the ground up and maintain it (as they used to in the past), that's a huge drain on development time.  You wouldn't be seeing near the capabilities you have now.

Yes, updates can take some time.  They can break things.  They may introduce new bugs while solving old ones.  Updating software should be approached with all deliberate intent, when there is time to spend to do it right (which includes rolling back if necessary).

[andrei_bursuc]

dgorsman spoken like a true fanboy. 

[andrei_bursuc]

if you have more updates like 7 in number in my case because i use max 2106, i waste an entire day with those stupid updates.

[andrei_bursuc]

Autodesk has become the EA of CG.

[spacefrog_]

Got nothing to do with dotnet c#, c++ or any of that level of tech. It's plain simple the silly microsoft installer patching in connection with the horrible mess and failed concept that the windows registry is. At least if you follow Microsoft by the book and log and register each and every little <1Kb icon file in the installer registry database. And on top of that, do that again and again and redundantly during the whole update run

All this mess explodes if you launch a patch cycle where the installer again and again does checksum tests from new files against existing files and constantly reads and queries the registry at the same time

Its a result of overzealous logging mania ...

There are about 40k files in the Max installers ( at least last time i checked) an all this verification and logging into registry takes the time

[3d-labor]

Surprise, surprise: The Update 3 for MAX 2019 also takes a looooooooooooong time! Time for AutoDESK to write a warning message before the update begins. "Attention! Update process takes a lomg time. In case you have a deadline this evening it´s better to do the update tomorrow!" And a second message: "Don´t believe, the update process has stopped, even if the progress bar seems to freeze for 10 minutes." This is no joke, this is absolutely neccesary information for the user!

[whitebirchstudios]

It has always been a pain to install MAX and any updates. I remember a while back, when I was managing a few dozen machines, I use a command line installer and it took minutes, instead of hours.

[3d-labor]

My Threadripper 2950x did the update in about 30minutes, my i7-3930k hangs in the middle of the progress bar since 20 minutes. Only one task named "Autodesk 3ds Max 2019 Update-Setup" but there are two processes of the "3dsMAX 2019.3_Uupdate.exe*32" in the task manager. Both seems to be working.  I will go to bed now and hope, it is ready tommorow! According to the Microsoft explainations mentioned above it can take "tens of minutes" to do the so called Native Image Generation.

[3d-labor]

Edit this morning: after 3 attempts: Update 3 installation fails every time after 50% (progress bar). The task is running and has two "....Update_3.exe*32" processes. When I cancel the task nothing happens. Only an additional  3rd process "....Update_3.exe*32" is now visible. Only killing these processes bring the task down. After that MAX2019.2 is working fine again. Also the Distrubuted Rendering with VRay and Backburner are working, even with MAX2019.3 installed on the render node. BTW the installaton of the VRay Next Update 1 was ready after 2 minutes.....

[3d-labor]

Now I was able to update the 3rd Update of MAX 2019.

After I had problems to load a scene file I decided to try to update once more. Additional to shut off Kaspersky Internet Security I stopped some other processes: Display Fusion (Monitor Management) , Listary (Search tool), Xonar Audio (Soundcard) and  3dconnexion (3d mouse). And now I had a surprise. After starting the Update.exe the progress bar jumped to over 50% in no time and when it dissapeared and I get an "Update successful" message window. After I startet I saw under "Help" --> " About" , that the update really was successfull. Hope it helps someone with similar problems.

[jibijib]

35 minutes into an install on 2020.3 (manual) update

Everything is from the HD or MS dot.net files over work's 200MB internet connection (1GB in a few seconds).

[whitebirchstudios]

Yep, and AD will pretend it is the first that they have heard of it when I have been inquiring why so slow for years.

[whitebirchstudios]

Waiting for over an hour for an update on a new PC. Frustration as heck.

[brian2burnett]

The patching system sucks.  They spent so much time optimizing the installers.  3ds Max 2020 8+ GB install takes 10 min.  update 2020.3 800 MB takes 45 min to install.   WTF!  just did 4 installs and it's like watching paint dry to get those patches installed.  

Optimize the Patching system already, Autodesk!

[darksilicon]

C# is .net and in many cases its way better than C++ stability wise. Just chill... with windows you get power and responsibility.

[brian2burnett]

The full product install is 10-15min. The patch takes 45-50min. Installed
on a bunch of systems now...same thing each time. If this is true, the
full product install, which is 10GB, should take 8 hours.