New activation code till end of March 2015 doesn't work

[Rustle]

Confirming activation problems and work around works

I couldn't find the version.txt file that derschulmeister was talking about. I found other files that did say 1.9.1 within them, anyone else have ideas?

[OllieB]

Just change your system date to Jan 29th, start MakeMKV and enter the license key posted a couple of messages ago. Restart MakeMKV and it works without a problem

[nathan]

I found the following solution. In my user-directory (c:\user\%username%\makemkv\) i found the file dump_ID4_F2_265BD3EB651976A1.tgz. I opend this with 7zip. Then I found the file dump_ID4_F2_265BD3EB651976A1.tar and opend it also in 7zip. In this archive I found the file version.txt. I have installed makemkv version 1.9.1 but in the file version.txt was the version number still 1.8.13. After changing the the version number to 1.9.1 in texteditor and aktualisation of the archive-file was all ok. Best regards! Sorry forget it - using Windows 7.

Could not find this file, in that location I have MKB_v31_SWATH_G55.tgz, it seems to contain files relating to the optical drive.

Currently using the change date workaround. Made me smile to see that windows predicts I will have a previous version "Later this week" on 01/02/2015.

[mattias83]

Just change your system date to Jan 29th, start MakeMKV and enter the license key posted a couple of messages ago. Restart MakeMKV and it works without a problem

I don't want to mess with my system sate - that will throw off other software I use.

[mattias83]

I found the following solution. In my user-directory (c:\user\%username%\makemkv\) i found the file dump_ID4_F2_265BD3EB651976A1.tgz. I opend this with 7zip. Then I found the file dump_ID4_F2_265BD3EB651976A1.tar and opend it also in 7zip. In this archive I found the file version.txt. I have installed makemkv version 1.9.1 but in the file version.txt was the version number still 1.8.13. After changing the the version number to 1.9.1 in texteditor and aktualisation of the archive-file was all ok. Best regards! Sorry forget it - using Windows 7.

Okay, this is weird. I didn't change the date or anything. I just started it up today and now MakemKV works fine. I'm ripping a disc now.

Could it be the new key wasn't set to be active until the first of the month?

The only other thing I can think of is I ran ccleaner last night - could that have cleared out some temporary junk file that was causing the issue?

[chuck666]

I had to use the Jan 29 date change workaround today, Feb 1.

[thedigitalhobo]

I upgraded to 1.9.1 this morning and its working fine.
No key required and says I'm good until April 21, 2015 (78 days)

[Viseman]

I upgraded to 1.9.1 this morning and its working fine.
No key required and says I'm good until April 21, 2015 (78 days)

Thats until this program works, it has nothing to do with the key.

[ssizzl]

I tried cclean and it didn't help. I have tried everything (other than changing the date) and it still doesn't work. I hope there is a fix for this. I had nightmares of it never working again LOL. However, one just needs to change the date until you restart makemkv. You can then change the date back while the disk gets backed up. Don't know what will happen after it finishes the current disk, but changing the date before every use is no big deal.

[mrkeeling]

Confirming activation problems and work around works (changing system date).

[ZeroGeek1979]

I am also having the same issue. Thank you for the date work around, as that did make the software start functioning again. Hopefully this is resolved soon!

[sofakng]

This doesn't work for me. If I set the date to 1/29 then it works, but re-entering the key using the instructions doesn't work once I set the date back to the current date.

[ssizzl]

This what I did.
- Change date
- Start Makemkv
- enter key
- restart makemkv
- change date back
- Leave makemkv running or you must repeat above.

[sparktank]

So, aside from the aformentioned workaround, is there any news from Mike about what's going on?

Is it leaving Beta?

[onthebeach]

I was experiencing the same issue today. I remembered I had previously updated to 1.9.1 in January.

The workaround I successfully used:

1. I grabbed the previous version 1.9.0 from: /download/old/
2. Uninstalled 1.9.1
3. Installed 1.9.0
4. Registered the new key
5. Confirmed the package was working
6. Installed 1.9.1 again
7. Confirmed software id working as normal.