Office error: “We weren't able to register your device and add your account to Windows.”












0















Full error




Something went wrong



We weren't able to register your device and add your account to
Windows. Your access to org resources may be limited.




History



Due to a local domain issue, I had to remove my PC from the domain and re-add it. After that my user profile was broken so I used a tool to migrate it. Upon logging in, all my settings were back but I was not logged into my Office 365 apps. When I try to, I get the error above.



After lots of troubleshooting, I created a new local account on my PC and was able to successfully set up Office and login as expected.



Question



How can I fix my current domain-based Windows profile so that I can login to Office using my Office365 credentials?










share|improve this question




















  • 1





    There are certain limitations to Volume License activation, in particular, the number of activations that must happen at once. Contact your network administrator for assistance.

    – Ramhound
    Aug 29 '18 at 18:23











  • Why was I able to "activate" it under a new local profile? I don't think this is a licensing thing...

    – Scott Beeson
    Aug 29 '18 at 18:26











  • Is your situation the one solved in the last entry on this post?

    – harrymc
    Aug 29 '18 at 18:35











  • No, that mentions a "DatabaseNotFoundException" error which I don't get. Also, the fix is to login to outlook.live.com which I cannot do with an Office365 account. That problem is in no way related to this as far as I can tell.

    – Scott Beeson
    Aug 29 '18 at 18:36






  • 1





    @ScottBeeson - Likely due to the fact the group policy was applied to the machine. You certainly can log into outlook.live.com with an Office 365 account. Both are Microsoft accounts (not saying it will fix anything though)

    – Ramhound
    Aug 29 '18 at 20:39
















0















Full error




Something went wrong



We weren't able to register your device and add your account to
Windows. Your access to org resources may be limited.




History



Due to a local domain issue, I had to remove my PC from the domain and re-add it. After that my user profile was broken so I used a tool to migrate it. Upon logging in, all my settings were back but I was not logged into my Office 365 apps. When I try to, I get the error above.



After lots of troubleshooting, I created a new local account on my PC and was able to successfully set up Office and login as expected.



Question



How can I fix my current domain-based Windows profile so that I can login to Office using my Office365 credentials?










share|improve this question




















  • 1





    There are certain limitations to Volume License activation, in particular, the number of activations that must happen at once. Contact your network administrator for assistance.

    – Ramhound
    Aug 29 '18 at 18:23











  • Why was I able to "activate" it under a new local profile? I don't think this is a licensing thing...

    – Scott Beeson
    Aug 29 '18 at 18:26











  • Is your situation the one solved in the last entry on this post?

    – harrymc
    Aug 29 '18 at 18:35











  • No, that mentions a "DatabaseNotFoundException" error which I don't get. Also, the fix is to login to outlook.live.com which I cannot do with an Office365 account. That problem is in no way related to this as far as I can tell.

    – Scott Beeson
    Aug 29 '18 at 18:36






  • 1





    @ScottBeeson - Likely due to the fact the group policy was applied to the machine. You certainly can log into outlook.live.com with an Office 365 account. Both are Microsoft accounts (not saying it will fix anything though)

    – Ramhound
    Aug 29 '18 at 20:39














0












0








0








Full error




Something went wrong



We weren't able to register your device and add your account to
Windows. Your access to org resources may be limited.




History



Due to a local domain issue, I had to remove my PC from the domain and re-add it. After that my user profile was broken so I used a tool to migrate it. Upon logging in, all my settings were back but I was not logged into my Office 365 apps. When I try to, I get the error above.



After lots of troubleshooting, I created a new local account on my PC and was able to successfully set up Office and login as expected.



Question



How can I fix my current domain-based Windows profile so that I can login to Office using my Office365 credentials?










share|improve this question
















Full error




Something went wrong



We weren't able to register your device and add your account to
Windows. Your access to org resources may be limited.




History



Due to a local domain issue, I had to remove my PC from the domain and re-add it. After that my user profile was broken so I used a tool to migrate it. Upon logging in, all my settings were back but I was not logged into my Office 365 apps. When I try to, I get the error above.



After lots of troubleshooting, I created a new local account on my PC and was able to successfully set up Office and login as expected.



Question



How can I fix my current domain-based Windows profile so that I can login to Office using my Office365 credentials?







windows-10 office365






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 29 '18 at 18:23









harrymc

256k14268568




256k14268568










asked Aug 29 '18 at 17:58









Scott BeesonScott Beeson

59752254




59752254








  • 1





    There are certain limitations to Volume License activation, in particular, the number of activations that must happen at once. Contact your network administrator for assistance.

    – Ramhound
    Aug 29 '18 at 18:23











  • Why was I able to "activate" it under a new local profile? I don't think this is a licensing thing...

    – Scott Beeson
    Aug 29 '18 at 18:26











  • Is your situation the one solved in the last entry on this post?

    – harrymc
    Aug 29 '18 at 18:35











  • No, that mentions a "DatabaseNotFoundException" error which I don't get. Also, the fix is to login to outlook.live.com which I cannot do with an Office365 account. That problem is in no way related to this as far as I can tell.

    – Scott Beeson
    Aug 29 '18 at 18:36






  • 1





    @ScottBeeson - Likely due to the fact the group policy was applied to the machine. You certainly can log into outlook.live.com with an Office 365 account. Both are Microsoft accounts (not saying it will fix anything though)

    – Ramhound
    Aug 29 '18 at 20:39














  • 1





    There are certain limitations to Volume License activation, in particular, the number of activations that must happen at once. Contact your network administrator for assistance.

    – Ramhound
    Aug 29 '18 at 18:23











  • Why was I able to "activate" it under a new local profile? I don't think this is a licensing thing...

    – Scott Beeson
    Aug 29 '18 at 18:26











  • Is your situation the one solved in the last entry on this post?

    – harrymc
    Aug 29 '18 at 18:35











  • No, that mentions a "DatabaseNotFoundException" error which I don't get. Also, the fix is to login to outlook.live.com which I cannot do with an Office365 account. That problem is in no way related to this as far as I can tell.

    – Scott Beeson
    Aug 29 '18 at 18:36






  • 1





    @ScottBeeson - Likely due to the fact the group policy was applied to the machine. You certainly can log into outlook.live.com with an Office 365 account. Both are Microsoft accounts (not saying it will fix anything though)

    – Ramhound
    Aug 29 '18 at 20:39








1




1





There are certain limitations to Volume License activation, in particular, the number of activations that must happen at once. Contact your network administrator for assistance.

– Ramhound
Aug 29 '18 at 18:23





There are certain limitations to Volume License activation, in particular, the number of activations that must happen at once. Contact your network administrator for assistance.

– Ramhound
Aug 29 '18 at 18:23













Why was I able to "activate" it under a new local profile? I don't think this is a licensing thing...

– Scott Beeson
Aug 29 '18 at 18:26





Why was I able to "activate" it under a new local profile? I don't think this is a licensing thing...

– Scott Beeson
Aug 29 '18 at 18:26













Is your situation the one solved in the last entry on this post?

– harrymc
Aug 29 '18 at 18:35





Is your situation the one solved in the last entry on this post?

– harrymc
Aug 29 '18 at 18:35













No, that mentions a "DatabaseNotFoundException" error which I don't get. Also, the fix is to login to outlook.live.com which I cannot do with an Office365 account. That problem is in no way related to this as far as I can tell.

– Scott Beeson
Aug 29 '18 at 18:36





No, that mentions a "DatabaseNotFoundException" error which I don't get. Also, the fix is to login to outlook.live.com which I cannot do with an Office365 account. That problem is in no way related to this as far as I can tell.

– Scott Beeson
Aug 29 '18 at 18:36




1




1





@ScottBeeson - Likely due to the fact the group policy was applied to the machine. You certainly can log into outlook.live.com with an Office 365 account. Both are Microsoft accounts (not saying it will fix anything though)

– Ramhound
Aug 29 '18 at 20:39





@ScottBeeson - Likely due to the fact the group policy was applied to the machine. You certainly can log into outlook.live.com with an Office 365 account. Both are Microsoft accounts (not saying it will fix anything though)

– Ramhound
Aug 29 '18 at 20:39










2 Answers
2






active

oldest

votes


















1














I know this is an old post but this might help someone out there.
I forgot I had an existing installation of Office 365 and I keep getting the above error. I ran these commands in CMD (open as admin):



cscript.exe "%ProgramFiles(x86)%Microsoft OfficeOffice16ospp.vbs" /dstatus


Take note of the last 5 digits of the product key. Then run this command:



cscript.exe "%ProgramFiles(x86)%Microsoft OfficeOffice16ospp.vbs" /unpkey:XXXX


(replace the XXXX with the last 5 chars of the prod key):



This is only recommended for users who have Office Apps with Office 365 license.



Reference here






share|improve this answer

































    -1














    This worked for me:



    HKCUSOFTWAREMicrosoftOffice16.0CommonIdentityEnableADAL
    REG_DWORD
    Value: 0



    This disables modern authentication for office applications.






    share|improve this answer





















    • 1





      Can you add some detail and explanation? Please do not respond in comments; edit your answer to make it clearer and more complete.

      – Scott
      Jan 5 at 1:06











    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1353510%2foffice-error-we-werent-able-to-register-your-device-and-add-your-account-to-w%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    I know this is an old post but this might help someone out there.
    I forgot I had an existing installation of Office 365 and I keep getting the above error. I ran these commands in CMD (open as admin):



    cscript.exe "%ProgramFiles(x86)%Microsoft OfficeOffice16ospp.vbs" /dstatus


    Take note of the last 5 digits of the product key. Then run this command:



    cscript.exe "%ProgramFiles(x86)%Microsoft OfficeOffice16ospp.vbs" /unpkey:XXXX


    (replace the XXXX with the last 5 chars of the prod key):



    This is only recommended for users who have Office Apps with Office 365 license.



    Reference here






    share|improve this answer






























      1














      I know this is an old post but this might help someone out there.
      I forgot I had an existing installation of Office 365 and I keep getting the above error. I ran these commands in CMD (open as admin):



      cscript.exe "%ProgramFiles(x86)%Microsoft OfficeOffice16ospp.vbs" /dstatus


      Take note of the last 5 digits of the product key. Then run this command:



      cscript.exe "%ProgramFiles(x86)%Microsoft OfficeOffice16ospp.vbs" /unpkey:XXXX


      (replace the XXXX with the last 5 chars of the prod key):



      This is only recommended for users who have Office Apps with Office 365 license.



      Reference here






      share|improve this answer




























        1












        1








        1







        I know this is an old post but this might help someone out there.
        I forgot I had an existing installation of Office 365 and I keep getting the above error. I ran these commands in CMD (open as admin):



        cscript.exe "%ProgramFiles(x86)%Microsoft OfficeOffice16ospp.vbs" /dstatus


        Take note of the last 5 digits of the product key. Then run this command:



        cscript.exe "%ProgramFiles(x86)%Microsoft OfficeOffice16ospp.vbs" /unpkey:XXXX


        (replace the XXXX with the last 5 chars of the prod key):



        This is only recommended for users who have Office Apps with Office 365 license.



        Reference here






        share|improve this answer















        I know this is an old post but this might help someone out there.
        I forgot I had an existing installation of Office 365 and I keep getting the above error. I ran these commands in CMD (open as admin):



        cscript.exe "%ProgramFiles(x86)%Microsoft OfficeOffice16ospp.vbs" /dstatus


        Take note of the last 5 digits of the product key. Then run this command:



        cscript.exe "%ProgramFiles(x86)%Microsoft OfficeOffice16ospp.vbs" /unpkey:XXXX


        (replace the XXXX with the last 5 chars of the prod key):



        This is only recommended for users who have Office Apps with Office 365 license.



        Reference here







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Nov 13 '18 at 16:34









        Mr Shunz

        1,75111817




        1,75111817










        answered Nov 13 '18 at 14:47









        SavageTofuSavageTofu

        111




        111

























            -1














            This worked for me:



            HKCUSOFTWAREMicrosoftOffice16.0CommonIdentityEnableADAL
            REG_DWORD
            Value: 0



            This disables modern authentication for office applications.






            share|improve this answer





















            • 1





              Can you add some detail and explanation? Please do not respond in comments; edit your answer to make it clearer and more complete.

              – Scott
              Jan 5 at 1:06
















            -1














            This worked for me:



            HKCUSOFTWAREMicrosoftOffice16.0CommonIdentityEnableADAL
            REG_DWORD
            Value: 0



            This disables modern authentication for office applications.






            share|improve this answer





















            • 1





              Can you add some detail and explanation? Please do not respond in comments; edit your answer to make it clearer and more complete.

              – Scott
              Jan 5 at 1:06














            -1












            -1








            -1







            This worked for me:



            HKCUSOFTWAREMicrosoftOffice16.0CommonIdentityEnableADAL
            REG_DWORD
            Value: 0



            This disables modern authentication for office applications.






            share|improve this answer















            This worked for me:



            HKCUSOFTWAREMicrosoftOffice16.0CommonIdentityEnableADAL
            REG_DWORD
            Value: 0



            This disables modern authentication for office applications.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited yesterday









            Community

            1




            1










            answered Jan 5 at 0:40









            Misty QuaintanceMisty Quaintance

            1




            1








            • 1





              Can you add some detail and explanation? Please do not respond in comments; edit your answer to make it clearer and more complete.

              – Scott
              Jan 5 at 1:06














            • 1





              Can you add some detail and explanation? Please do not respond in comments; edit your answer to make it clearer and more complete.

              – Scott
              Jan 5 at 1:06








            1




            1





            Can you add some detail and explanation? Please do not respond in comments; edit your answer to make it clearer and more complete.

            – Scott
            Jan 5 at 1:06





            Can you add some detail and explanation? Please do not respond in comments; edit your answer to make it clearer and more complete.

            – Scott
            Jan 5 at 1:06


















            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1353510%2foffice-error-we-werent-able-to-register-your-device-and-add-your-account-to-w%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

            Mangá

             ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕