1 Reply Latest reply on Dec 6, 2013 1:06 PM by sjpt

    Cannot change authorisation, ID is blocked




      I downloaded an e-book from an online shop and my computer asked me to authorise. As it already has been authorised I pushed the button "continue without authorisation" and now I cannot transfer my e-book from the library to my e-book reader. When I want to authorise the computer the Adobe progamme says that it already has been authorised and that my ID is blocked. Yes, it is! By myself! So how can I change that? I do not have a second e-mail address to creat a new ID. There must be an option to change the authorisation. So please let me know what to do.

        • 1. Re: Cannot change authorisation, ID is blocked
          sjpt Level 4

          You got trapped by the terrible DRM infrastructure and ADE software.


          Before you do anything else, recover that book (see ~~~  below).


          Then, for future use, deregister ADE/your computer using ctrl-shift-D to ADE (cmd-shift-D on Mac).

          Then reauthorize with the ID you generally use and it should work OK.



          This is a vicious trap that Adobe lays for unsuspecting customers.

          When you register 'without ID', ADE creates an anonymous/implicit ID with limited powers (eg can't be used to share with other devices).

          Whenever you first load a DRM book, that copy of the book is associated with whatever ID the computer is registered to at the time.

          Any book you load while this anonymous ID is active gets associated with that ID, and can't be read on any other device.

          When you properly register your computer with a real ID, that old anonymous ID is lost.

          Now you don't have any devices that can read the book.


          The only way I know round this is to use a DRM stripper such as epubee BEFORE you deauthorize the device.

          I do NOT advocate using such code to get around the valid limitations placed on a DRM book.

          However, where the problem arises only because of the ineptness of Adobe's ADEPT DRM infrastructure and its implementation,

          such a measure is totally justifiable.