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

[Gardenman]

I would not do this but It makes a person think about not paying for books.

[Uncle Robin]

Originally Posted by Gardenman

I would not do this but It makes a person think about not paying for books.

Indeed. It's neither justification nor excuse but the argument "you wouldn't steal a paper book" does not address the issue that having bought a paper book one's ownership of it is far more stable than is true of ebooks.

[odamizu]

Originally Posted by JoeC

... 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.

Since you are on Mac, you might want to add a dummy file named "updates" to your Application Support > Kindle folder, otherwise I suspect 1.17.1 will auto-update again. Details here

[JoeC]

Originally Posted by odamizu

Since you are on Mac, you might want to add a dummy file named "updates" to your Application Support > Kindle folder, otherwise I suspect 1.17.1 will auto-update again. Details here

THANK YOU!!

[j.p.s]

Originally Posted by haertig

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".

Yep.

In this specific case, it appears that KindleForPC has been a long-time trusted program.

It looks like this trust has been misplaced for a long time since the back door had to be in place since at least 1.17

[gandoe]

I too, had this same incident happen....KfPC 1.17 working fine for over a year now, with update option unchecked. (BTW, I'm on Win 7, and so no longer get Win sys updates).

A weeks or so ago, I had the unexpected KfPC update, and spent some time:
- uninstalling, reinstalling KfPC 1.17, and immediate unapproved upgrade
- uninstalling again, cleaning registry, reinstalling KfPC 1.17, and immediate unapproved update
- uninstalling again, cleaning registry, deleting Kindle related program and content folders, reinstalling KfPC 1.17, and immediate unapproved update
...
I finally managed to eliminate the behavior by:
- uninstalling again, cleaning registry, deleting Kindle related program and content folders, Removing all related registered Kindle devices on Amazon site, reinstalling KfPC 1.17, with no further misbehavior.

Since I have standardized my ebook reading (obtaining content from from a variety of sources) using a different reader application and on a different Android device than a Kindle, this is EXACTLY why I choose to remain on KfPC 1.17.

Thought my experiences might shed some additional light on potential workarounds.

[JSWolf]

Why do we have another thread on the exact same topic? They should be merged with this one since this one has a better thread title.

[j.p.s]

Originally Posted by JSWolf

Why do we have another thread on the exact same topic? They should be merged with this one since this one has a better thread title.

I agree on both points, but an even better title would mention Kindle 4 Mac.

[riothamus]

Originally Posted by j.p.s

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

Thanks for the link. I hadn't found that thread yet. I did determine that with the calibre kfx plug-in I can still import books and the metadata will correctly transfer.i just have to search for the awz file type in my kindle content folder and drag and drop the files to calibre.

I'll still try out the methods in the other thread as it will help cut down on a step.

[JSWolf]

Originally Posted by j.p.s

I agree on both points, but an even better title would mention Kindle 4 Mac.

Change the word PC in the topic to Computer and that would incorporate both PC & MAC.

[crane3]

I got lucky. I had purchased the new Bujold book about Penric & Desdemona a couple of days ago & it was able to do the Calibre bit.

After reading the thread this time I decided to check the kindle for pc a short while ago & found that I also got "updated" to 1.30 & the time listed was when the k3pc was opened for checking.......whewwwwwww.

Did the delete on the 'my contents' folder BUT I had relocated my kindle library to another partition on a different disk drive. And since I made it on time, the deletion of the contents in the Documents folder was not needed nor a redownload required as there was nothing with the new file formats.

Looks like there is a need to check every so often & to checking when buying any books.

[haertig]

Originally Posted by JSWolf

Change the word PC in the topic to Computer and that would incorporate both PC & MAC.

Hey! You can't just say "Kindle for PC" and "Kindle for MAC".

What about us folks that run "Kindle for PC, under WINE, on Linux"???

And what about the "Kindle for PC, in a Virtual Machine, on a Blade server" group? Can't leave them out either.

There's gotta be "Kindle for DOS" and "Kindle for mainframes with punch cards and line printers" groups out there somewhere too.

It just ain't fair, I tell 'ya. Us non-Windows users are always getting left out of the brotherhood...

[Uncle Robin]

Originally Posted by haertig

There's gotta be "Kindle for DOS" and "Kindle for mainframes with punch cards and line printers" groups out there somewhere too. .

And what about those of us running "Kindle for the Babbage Engine"?

[johnnyb]

As long as the Kindle 3 is still supported at least we can still download books from the Amazon webpage.

[tas03]

gandoe: You mention removing "(r)emoving all related registered Kindle devices on Amazon site." What were the Kindle devices? Did you later restore them and did things remain OK? Thanks.