I'll consider it but I've got 2020 running just fine so the likelihood of me actually finding the ambition to do that is pretty low right now. I hope you don't take that personally or anything.

After I replaced my hard drives I installed 2020 and then tried to install 2021. 2021 didn't take, obviously, but it was different than what it's doing now. The install failed but I still had a directory for it in my start menu, but all the icons were blank. At that point is when I tried to run the uninstaller - tried both uninstall and repair, neither worked. Since then I had cleared absolutely every file associated with 2021 off of my computer (that I know of). Initially I had cleared out the registry manually and thought I got it all, but then after I ran CCleaner I saw there were a handful of files I had missed in some of the registry nooks and crannies. Anyways, figured that app had everything cleared out and I'd be good to go. No such luck. To answer your question, there's nothing I can see at this point either in the registry or in the C drive related to 2021. If I run the uninstaller right now it tells me the process is interrupted before the wizard is able to finish.

I've been in contact with them. They sent me step-by-step instructions which I followed to the T. Cleared out the registry, ran CCleaner, install. Same deal. Sent them the log file 42 hours ago...still waiting on a reply.

Gave it a shot. No dice.

2012, 2013 were installed, so I "repaired" them and they went. The 2017 file setup fails because another version is already installed. Looks like the file is trying to install 14.15.26706 and I currently have 14.22.27821.0 installed. Do I need to uninstall the latter and install the former?

Have not gotten anywhere with it, Chris. Had instructions from my reseller yesterday that I followed and gave same result. I navigated to the folder and the MSI file was, indeed, not there. I took the MSI file out of the full download folder and popped it into the screenshot folder for kicks. The errors on those screenshots are no longer popping up but it still results in a failed install. The second log that I posted are the results from after I had done that.

Started happening to me when I started using 2020. I lock all of my planes now.

I'll give it a shot. I replaced my hard drives a couple weeks ago so it was fresh installs right off the website after everything was back up and running. 2020 installed without a hitch, so who knows.

Did a hard reboot, yes. Same result. I'm waiting on a call back from my reseller right now. The last install I tried to do I pointed it to the Mastercam_Installer.msi file located in the extracted files from the zip. The errors don't pop up anymore and it still says failed. Log's changed a bit. Mastercam 2021-INSTALL_08-10-20_13-40-51.log

Posting the log file for anyone that's interested... Mastercam 2021-INSTALL_08-10-20_13-18-40.log

Setup has installed MSXML 6.0 Parser Successfully .NET Framework 4.6.1 or a later update is already installed on this computer Windows update standalone installer gives me an error message I tried it directly out of the downloads file and right now I"m attempting straight off the desktop with same results. Tried installing to my secondary hard drive but no luck there.

Just tried it with Microsoft Defender turned off. Same result. Running setup prerequisites and running the install isn't appearing to make a difference either. Unless I'm doing something wrong.

I like to live on the edge.

Trying the full install in a bit here. Not running anti-virus. How would I flag the install as safe?

Windows 10 Pro, build 19041.388 Notify me only when apps try to make changes to my computer Looks like .net framework is 4.8, which I think is the most recent.

Run as admin yields same results. Right now there's no Mastercam 2021 data in the registry, so that fix is a no-go, Josh.

Just grabbed this one fresh this morning. Trying the run as admin right now...

I'm having a difficult time installing 2021. I tried once a few weeks ago and it didn't go...had to go through and clear 2021 stuff out of the registry, plus search any stray 2021 files and clear those out too to pull it out of the apps list. Anyone seen these errors before or have any insight? I installed and am running 2020 just fine so this isn't any sort of emergency.

?????

I've got a file with 15 ops, and at one point it posted every single op to "default" RPM and feed values instead of what was programmed.

I haven't seen that but I have seen my "Override geometry diameter" box come in unchecked during an import. Not sure if it's supposed to happen but I learned the hard way that it does.

It'll post out the correct feedrate if I change it to something other than what I want, regen, change back to what I want, regen, post. It looks to me like if I create the cutter path and leave that override untouched it's posting out something above 100% until I make some sort of change to it and regen.

Anyone seen this one yet? I never typically program an override for a finish pass, but I've seen them posting out above 100% lately when they're programmed at 100%. If I go in and change the feedrate to something other than 100%, then back to 100%, regen, it'll post at what is programmed. This is in helix bore....haven't noticed it anywhere else at this point.

For posterity - in the mill-file.rpx file the New Page data in the report detail is defaulted to "Before". If that field is changed to none it won't break the page for each new NC name.

Bill, I believe I'm just using the original "Mill" template. I've done an absolute ton of modification! What I have it configured for is a very basic setup sheet...super minimal. So while it is derived from Active Reports it looks more like an in-depth tool sheet. I think the hierarchy I have in place is correct. For this particular setup sheet I'm pulling data from both the tool and operation fields and the output is fantastic. In the first column, however, I want to pull the NCFILE-NAME from the NCFILE field. Using tags or XML data I'm having success with pulling other data in from the NCFILE field (see my output with MACHINE-NAME BELOW).