May 19 2020 05:25 AM
Please help me, I'm stuck!
I installed the latest updates of Windows 10 Enterprise to version 10.0.19041 build 19041 from MSDN but I have a serious problem with the recognition of my Office 365 PRO Plus subscription.
The system shows me an error mask attached and I can no longer use Office 365.
I tried to completely remove Office 365 and reinstall it but without success.
Can someone help me?
Thanks
May 19 2020 05:32 AM
Hello,
Can you please translate the error message to English, so I can help you.
Regards.
May 19 2020 05:48 AM
There was a problem installing the product key. If the problem persists, try restoring the Office product. System error 0x80070005
May 19 2020 11:49 PM
Okay, please refer suggestions provided in this support article:
Hope this helps!
May 20 2020 02:06 AM
I have scrupulously followed the instructions found on the internet page relating to the topic but unfortunately I have not solved my problem.
I would like to specify that:
In order to better analyze my problem, go to the images of the errors found and I provide below the English translation of these messages:
I want to thank everyone for the attention and speed with which you are responding to my problem but as you can understand right now I am a bit desperate!
Thanks to all!
May 20 2020 03:09 AM - edited May 21 2020 12:37 AM
....
May 20 2020 03:15 AM - edited May 21 2020 12:37 AM
....
May 20 2020 08:07 AM
SolutionInformation: I finally solved my problem!
Not being able to manually update Office 365, I downloaded the offline version from the monthly channel and more precisely the version "16.0.12730.20270".
That way, after trying twice to log in, the system recognized me correctly.
Thanks to everyone for the prompt answers.
Best Regards
May 20 2020 08:28 AM - last edited on May 20 2020 09:26 AM by Eric Starker
May 20 2020 08:28 AM - last edited on May 20 2020 09:26 AM by Eric Starker
If the 0x80070005 error started after updating Windows, you can fix the issue by updating the registry.
Notes:
WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved.
Before making any change in the registry, please back up your registry.
Close all Office apps.
Right-click the Windows button in the lower left-hand corner of your screen and select Run.
In the Open box, type regedit, and select OK.
Select Yes when prompted to allow Registry Editor to make changes to your device.
In the Registry Editor, expand HKEY_USERS and select S-1-5-20.
Right-click S-1-5-20 and select Permissions.
Select Add.
Type the logged in user's name, select Check Names, and then select OK.
Select Advanced.
In Advanced Security Settings, on the Permissions tab, select the user you just added, and then select Edit.
Under Basic permissions, select Full Control, and then select OK.
This takes you back to Advanced Security Settings.
In Advanced Security Settings, on the Permissions tab, select NETWORK SERVICE, and then select Edit.
Under Basic permissions, select Full Control (if not already selected), and then select OK.
This takes you back to Advanced Security Settings.
In Advanced Security Settings, select the checkbox named Replace all child object permission entries with inheritable permission entries form this object and select OK.
Close Registry Editor and restart any Office app to try activating again.
I hope this helps!
Regards.
Admin
May 21 2020 08:17 AM
I had solved the problem but unfortunately there is a script on my company PC that downgrades me to version 1808 (build 10730.20264). With this version of Office 365, my subscription is not recognized.I tried to put @Abigail05's suggestions into practice but I can't find the user "NETWORK SERVICE". I'm stuck again :(
May 20 2020 08:07 AM
SolutionInformation: I finally solved my problem!
Not being able to manually update Office 365, I downloaded the offline version from the monthly channel and more precisely the version "16.0.12730.20270".
That way, after trying twice to log in, the system recognized me correctly.
Thanks to everyone for the prompt answers.
Best Regards