old threadrippers and win11 upgrade?

[Jens]

We have a couple of 3990x workstations at the office, and IT wants us to change them as they do not meet requirements to update to win11. Primarily due to not supporting TPM 2.0 protocol (what ever that is).

I googled a bit and found a way to enable this in the BIOS. So in theory, there should no longer be an issue in "upgrading" to win 11. I'd rather stay with win 10, but due to company policy we have to update one way or the other.

Now to my question: Has anyone of you guys been in a similar situation and are now running win11 without issues on older threadripper CPUs?

[arqrenderz]

You can run Win 11 bypassing the tpm requirements  https://www.makeuseof.com/rufus-bypass-tpm-secure-boot-requirements-windows-11/
You can buy a tpm module for 10 euros if you want to keep it.
IT departments are a bad joke most of the times.
If the office doesnt know what to do with too much cash on hand it could raise salarys, buy new hardware, hire better IT or just pocket it ;)

[Vuk]

I would suggest not upgrading. One of my old Threadrippers has upgraded to win 11 overnight and after that, I just couldn't fix the network adapter not working issue.

Sadly there are no stable drivers or working drivers for the integrated LAN card on the board for WIN 11. I don't remember if it was Realtek or Intel but I just rerolled back to win 10.

[alexyork]

We have a bunch of 3990x and they're all compatible out of the box with win11 if we wanted, but you might just need to enable the bios' TPM and/or update the motherboard BIOS version for this to be visible.

[Nejc Kilar]

Yup, can confirm. Just flip the TPM setting to firmware (or anything but disabled) and the Zen 2 / Zen 3 Threadrippers work with Windows 11 :)

[TomG]

My personal non-work machine is still on Win 10, because the motherboard does not have TPM 2 (it's a motherboard thing, not a processor thing). There is TMP 2 emulation via the processor, but turning this on gave lag on all my audio applications and since my hobby is music, this was totally unacceptable, meaning without buying a whole new motherboard there is no way to get my personal machine on Win 11. Which I am fine with :) I am not sure if TPM emulation on the processor has got any better, but I simply not taking any risks, as I can't afford to totally rebuild my personal machine :)

[maru]

I am not sure if TPM emulation on the processor has got any better, but I simply not taking any risks, as I can't afford to totally rebuild my personal machine :)

Yes, it did, such things are handled through BIOS updates. This should be perfectly safe unless using some very old motherboard/CPU I guess.

[Jens]

Thanks for the feedback guys. If it were up to me, I would 100% stay on windows 10, but it's a company IT policy that all must be on win 11 before summer.

I managed to turn the TPM 2.0 on via BIOS. Didn't notice anything changed when I got into windows and corona was working fine. I was then asked by IT to reboot so their win 11 auto upgrade would kick in.

It updated to win11 without issues (just took quite a while). However, the scene I was working on yesterday (pre win11), would not render. VFB starts up, but the corona smiley is not turning and nothing is happening under "stats" either. I tried doing IR, but then max crashed (asking if i wanted to autobackup).

Before this I got an openCL warning from max that asked me to update my GPU driver (makes sense, so I did that and haven't gotten the warning this time).

An empty scene with a box and corona sun + sky renders without issue.

I loaded max and the scene once again, isolated only 1 object, tried to render that and after some time it rendered. Then I unhide rest of scene and all rendered fine. Very odd. Will have to keep an eye on this.

"Loading Corona Assets" are also taking a few minutes on scene load - I thought this was fixed long ago? (I'm on v12 hotfix1)

Thank god I'm not on a tight project deadline right now :)

[maru]

It updated to win11 without issues (just took quite a while). However, the scene I was working on yesterday (pre win11), would not render. VFB starts up, but the corona smiley is not turning and nothing is happening under "stats" either. I tried doing IR, but then max crashed (asking if i wanted to autobackup).

Before this I got an openCL warning from max that asked me to update my GPU driver (makes sense, so I did that and haven't gotten the warning this time).

An empty scene with a box and corona sun + sky renders without issue.

I loaded max and the scene once again, isolated only 1 object, tried to render that and after some time it rendered. Then I unhide rest of scene and all rendered fine. Very odd. Will have to keep an eye on this.

I was dealing with an identical case today (or maybe the report/scene originally came from you? :) )
The solution was the good old "lock icon in Render Setup", so:
- Press Alt+W to show all viewports
- Open Render Setup
- Click on the viewport you want to render
- Lock the small lock icon at the top of the Render Setup window
- Then render
I hope this helps!

[Jens]

I was dealing with an identical case today (or maybe the report/scene originally came from you? :) )
The solution was the good old "lock icon in Render Setup", so:
- Press Alt+W to show all viewports
- Open Render Setup
- Click on the viewport you want to render
- Lock the small lock icon at the top of the Render Setup window
- Then render
I hope this helps!

I haven't submitted the scene, but it seems to still be an issue with the scene. On first scene load, it will not render. Just shows the VFB with the corona icon smiley (I'm using old interface) turned just a little bit. But nothing going on in stats, the render button is grayed out and "stop" is blue as it usually is when rendering. I noticed that the usual max pop up with "loading geometry" etc wasn't showing. I shut down max. This will keep happening, so I have to shut down max. Start it again, and then it works.

The icon lock is always on in my settings and haven't changed since pre the win 11 update, so don't think that is the case.

Interactive rendering + slate material editor open is a horrible experience on this CPU still (3990x). Even viewport is very laggy. Had hoped win11 would have fixed something.

I will do an archive and send to you to see if you can reproduce.

[maru]

The icon lock is always on in my settings and haven't changed since pre the win 11 update, so don't think that is the case.

The thing is 3ds Max sometimes switches the "view to render" internally and this results in an attempt to render a non-existent/broken viewport. The idea here is to disable the lock feature, make sure that the correct view is selected, and lock it again. I am just sharing it as it has recently helped with an identical issue.

[Jens]

The thing is 3ds Max sometimes switches the "view to render" internally and this results in an attempt to render a non-existent/broken viewport. The idea here is to disable the lock feature, make sure that the correct view is selected, and lock it again. I am just sharing it as it has recently helped with an identical issue.

ahh perfect, thank you for clarifying Maru. Will try and remember this fix. I have archived the scene and will upload now.

While it archived I downloaded Corona 12 update 1 HF1 just to see if it would change anything. Installed. Rebooted and started max and the scene. I clicked IR as the first thing after scene load. It opened VFB and seemed to start loading (memory consumption was going up steadily), but before render started, it instant crashed.

So will include that max log and mini dmp in the archive scene ticket. Just be aware that the archived scene is with Corona 12 HF1 and not "Update 1 HF1".
*submitted ticket with ID Request #349688"