QUESTION:

"I have been having trouble updating to version 15. Can you help?"

---

ANSWER:

Yes!! Definitely! It took us a couple days to sort out what was happening here. But, we've finally got it all figured out now. Yay!!

PC

A couple dozen PC users who have the Malwarebytes virus scanner installed on their computer were having trouble upgrading to Cook'n Version 15 because their virus scanner was quarantining the Cook'n Version 15 application due to a false positive.

We are still working with the company to have them update their definition files so this sort of thing doesn't happen anymore. But, unfortunately, all of their techs are out of the office until the end of next week for the holiday!

In the meantime, if you are running into this problem, click here for a super easy solution.

MAC

Mac users did not miss out on the fun either. There were a few dozen Mac users who were getting stuck in an upgrade loop. This one was super perplexing. I literally lost sleep over this because it was a riddle wrapped in a mystery inside an enigma.

As it turns out, most people got Cook'n by installing or upgrading to Cook'n X3 (Version 13). Those people had no problem upgrading to Cook'n Version 14 and then, eventually, to Cook'n Version 15.

However, a couple years ago, when a new version of the Mac operating system came out, some people were having trouble using Cook'n due to the new security protocols. So, as a super simple solution, we created a Cook'n Version 14 installer for just those people

Apparently, one of the folders in the Cook'n Version 14 installer did not have read/write privileges set properly. This did not cause any problems until Cook'n tried to auto-update itself when version 15 came out. Since the one folder was set with read-only privileges, the upgrade to Version 15 was failing.

Once we discovered the problem, the solution was simple. But, at first it was very difficult to figure out because Cook'n seemed to upgrade perfectly fine on some computers but not on others. The folder attributes were set properly on some systems but not on others and, for the life of me, we couldn't figure out why.

Now that we figured it out, the solution to this problem is super simple as well. If you are running into this problem, click here for a super easy solution.