Kindle for PC force updated to version 1.30.0--possible to revert to earlier version?

[John F]

Originally Posted by kirk8677

I tend to wonder if, at some point, Amazon will simply pull support entirely for version 1.17, and at that point de-DRMing books will not be possible, at least without some new piece of software or something else I'm not aware of.

This would be a sad day indeed for Calibre users, as one would be forced to stay in Amazon's woefully inadequate sandbox.

For people who own older Kindles, there will still be the download for transfer via USB hole?

[riothamus]

Twice now, once a few days ago and once just now it auto-updated to version 1.30 with no dialog box or other indication. If anyone can figure out how to disable this again (even with the auto update checkbox blank) I'd appreciate it.

All I can do is uninstall, delete the registry key, and reinstall 1.17. All I really want to do is import my Kindle library to Calibre for a duplicate book check. I don't even need de-drm, just importing the metadata to a book record in Calibre with no contained format. Version 1.17 is the easiest because it will download a .awz file that Calibre will import correctly.

[lkmiller]

Originally Posted by kirk8677

I tend to wonder if, at some point, Amazon will simply pull support entirely for version 1.17, and at that point de-DRMing books will not be possible, at least without some new piece of software or something else I'm not aware of.

This would be a sad day indeed for Calibre users, as one would be forced to stay in Amazon's woefully inadequate sandbox.

DeDRMing is possible through K4PC/Mac 1.26 without any modifications. And possible through the latest with some additional effort.

[j.p.s]

Originally Posted by riothamus

Twice now, once a few days ago and once just now it auto-updated to version 1.30 with no dialog box or other indication. If anyone can figure out how to disable this again (even with the auto update checkbox blank) I'd appreciate it.

All I can do is uninstall, delete the registry key, and reinstall 1.17. All I really want to do is import my Kindle library to Calibre for a duplicate book check. I don't even need de-drm, just importing the metadata to a book record in Calibre with no contained format. Version 1.17 is the easiest because it will download a .awz file that Calibre will import correctly.

Have you looked at the thread
https://www.mobileread.com/forums/sh...d.php?t=334278
where possible fixes are being suggested?

[haertig]

If a Windows update changed application settings in a non-Microsoft program, then the Windows programming team has some serious explaining to do!

[Terisa de morgan]

Originally Posted by haertig

If a Windows update changed application settings in a non-Microsoft program, then the Windows programming team has some serious explaining to do!

The application setting are the same: don't update automatically, but the program is updated in any case.

[JSWolf]

Originally Posted by haertig

If a Windows update changed application settings in a non-Microsoft program, then the Windows programming team has some serious explaining to do!

The fault lies with Amazon.

[JoeC]

Originally Posted by Dr. Drib

YES, IT HAPPENED...

This happened to me yesterday. And I've had mine NOT checked for automatic updates and have had it that way for a number of years.

I removed the new version and reinstalled (and made certain everything was the way it should be, of course), and then registered it on Amazon and now everything is fine.

I experienced the same thing. I think what happened originally is I opened a KFX book from the Kindle app (I wasn't paying close attention) and the app closed or reset. When I restarted it the app was on 1.30.

I reinstalled 1.17.1 from my a time machine backup made just before the forced update (whew!). Before I reinstalled I followed instructions regarding disabling KFX support on the Mac (https://www.mobileread.com/forums/sh...d.php?t=283371). And all well for the moment.

[JoeC]

Originally Posted by JSWolf

The fault lies with Amazon.

The fact that the Amazon Kindle app did a forced update on both Windows and Mac systems is a real head scratcher for me. I don't understand why the operating systems allow this without user interaction. This seems like a security concern to me.

[jhowell]

Originally Posted by JoeC

The fact that the Amazon Kindle app did a forced update on both Windows and Mac systems is a real head scratcher for me. I don't understand why the operating systems allow this without user interaction. This seems like a security concern to me.

Windows programs intended for use by a single user can be installed in the user's AppData/Local directory without an escalation of privileges. That is where Kindle for PC is installed by default.

[JoeC]

Thanks for the detail.

[haertig]

Originally Posted by haertig

If a Windows update changed application settings in a non-Microsoft program, then the Windows programming team has some serious explaining to do!

Some evidently didn't catch the intent of my response above. It was a satirical, rhetorical post.

[haertig]

Originally Posted by JoeC

The fact that the Amazon Kindle app did a forced update on both Windows and Mac systems is a real head scratcher for me. I don't understand why the operating systems allow this without user interaction. This seems like a security concern to me.

Programs run with the permissions allowed them - in this case, the permissions of the user that installed the program. You can certainly tighten things down after installation if you want - run things in a sandbox, manually set permissions, etc. - but by default if you trust the program enough to install it, that pretty much carries over that trust to let it run and do the things inherent to running. Creating, updating, deleting files, etc. In most cases, programs are well behaved. I would suggest that if KindleForPC has a setting you can engage for "Do not auto-update", but it ignores your choice and updates anyway, then it is NOT a "well behaved program". Quite the contrary. I would call it "malicious".

You are correct - a program being able to change things on your computer is very dangerous. That's why you often times see the warning, "Only install software that you trust!" You need to realize, that when you install a program on your computer, you are giving that program "the keys to your kingdom". Not 100% mind you, but you are giving it significant leeway by default. You can't expect the operating system to protect you from this by default. I doubt anybody would be terribly thrilled with an OS that kept pestering you, "Such-and-such application wants to write a line of text to it's logfile, do you want to allow this?" That would get old really fast.

Run a suspect program in a sandbox. Run it in a virtual machine. Save system snapshots before running it. OS'es can assist you in taking these precautions yourself, but they aren't going to do it for you by default.

In this specific case, it appears that KindleForPC has been a long-time trusted program. These programs can be trusted right up until the time they can't be trusted. We just crossed that threshold. There is no un-crossing it. KindleForPC can no longer be trusted. Period. We can continue using it, but prudent users will now start taking precautions.

[JoeC]

I have been primarily using a Mac for some time. I have become complacent in that any of the primary programs I use ask permission to be updated. I am not an expert by any means - no doubt there are some shenanigans in the background I'm unaware of.

[jackie_w]

Originally Posted by haertig

In this specific case, it appears that KindleForPC has been a long-time trusted program. These programs can be trusted right up until the time they can't be trusted. We just crossed that threshold. There is no un-crossing it. KindleForPC can no longer be trusted. Period. We can continue using it, but prudent users will now start taking precautions.

Prudent users might consider voting with their wallets and buying their books elsewhere. What incentive is there to behave less obnoxiously when people keeping throwing their money at them no matter what they do.