Corrupted File fix
This isn't a PF issue, but it is an oddity that I encountered while installing P3, that is worth filing away in case you run into something similar.
I am running win 10. I dl'd Perspectives 3 setup, but when I ran it I encountered a corrupted file message. I dl'd the setup file again, verified that I was logged in as admin, disabled Windows Defender and Walwarebytes anti-exploit (free edition), and re-booted before trying again.
First thing I noticed is that Win 10 automatically re-enabled Windows Defender on reboot (and apparently any time it has been disabled for any period of time). I re-disabled it and ran setup again only to get the corrupted file message.
I downloaded the setup file again (for the first time with AV programs disabled). This time setup ran fine.
So it seems that my AV program corrupted the setup file during download. DL'ing the file with AV off fixed the issue. I've never encountered this before, so I thought I'd share. I've already contacted Malwarebytes.
But add to the list, when addressing a failed install, to be sure AV is off during DL, not just during install.
Now, off to some mapping goodness!
I am running win 10. I dl'd Perspectives 3 setup, but when I ran it I encountered a corrupted file message. I dl'd the setup file again, verified that I was logged in as admin, disabled Windows Defender and Walwarebytes anti-exploit (free edition), and re-booted before trying again.
First thing I noticed is that Win 10 automatically re-enabled Windows Defender on reboot (and apparently any time it has been disabled for any period of time). I re-disabled it and ran setup again only to get the corrupted file message.
I downloaded the setup file again (for the first time with AV programs disabled). This time setup ran fine.
So it seems that my AV program corrupted the setup file during download. DL'ing the file with AV off fixed the issue. I've never encountered this before, so I thought I'd share. I've already contacted Malwarebytes.
But add to the list, when addressing a failed install, to be sure AV is off during DL, not just during install.
Now, off to some mapping goodness!
Comments
A few others reported similar problems in other and the solution that always worked was always turn of your anti-virus program when install a ProFantasy product for the install to work.
Security is necessary but can sometimes be a bit too aggressive. Add to that the higher security of the newer OS's and it makes ya wonder who own the machine. Sheesh!