Installing Max 6 on Windows 11 corrupts a Windows boot file. (Version 6.1.10, 32 and 64 bit)
I'm a loyal Max 6 user (and can't currently afford the upgrade to Max 7). Unfortunately, I just changed laptops to a Windows 11 machine... apparently, installing Max 6 on this new computer corrupts a "boot-critical file", forcing me to do a full system restore after my 1st restart. I have been working on several projects in Max 6 that I was planning to continue on the new machine, and between that and the multiple system restores I've had to do today, this is a MAJOR issue for me.
The problem started when I downloaded and ran the 32-bit Max 6 installer (v 6.1.10). On restarting my computer to confirm the changes I was given the classic "Your computer has run into a problem and needs to restart" screen (repeatedly), before automatic repair was attempted (and failed). Finally I was told to either boot in Windows 10, or wipe my hard drive. Luckily I found a recent system restore and didn't lose any work, but it was an extremely serious crash all the same.
I thought this may have been a problem with installing the 32-bit version, so I tried 64-bit instead. Same issue. On digging further, the log files of the crash identified the problem as:
"Boot critical file c:\efi\microsoft\boot\cipolicies\active\{cdd5cb55-db68-4d71-aa38-3df2b6473a52}.cip is corrupt."
What could be going on during installation that would modify the Windows boot files?? Is there any way I can continue using Max 6 on my new machine (without destroying it in the process)? Please help!
Max 6 itsefs needs no real installation,
you could simply copy Max 6 folder from old Laptop,
but Pace Interlok stuff does, and I am pretty sure that
this is causing the problem.
You could run Max runtime version to confirm that.
If there is solution to that ?
Hard to say, if one would install Windows 11 compatible
interlok drivers, would Max 6 accept and use that ?
I guess not.
Have you tried running Max 6 in compatibility mode for an older Windows version?
any solution to this ?
Its a real pain when you need to run stuff from the past that works on objects that are now out of date (eg 32 bit)
If that is so important,
make extra little partition and install win 10 32 bit
and trimm it down for using max,
can be done with 2- 3 GB system size at end.
Or install max 7 32 bit.
Yeah Ive tried these things but there is a couple of other problems that this doesnt seem to resolve, regarding a VST effect the installation used and a couple of other leap motion related issues. I actually have managed to install max 6 on a windows 10 computer now - but I have no idea how - for some mysterious reason it just worked, but unfortunately I cannot share why or repeat on othe rmachines.
You can run max 6 runtime wthout pace installed.
It is even better to run runtime for installations than max itself.