mirror of
https://github.com/massgravel/Microsoft-Activation-Scripts.git
synced 2026-04-26 14:35:49 +03:00
[GH-ISSUE #420] Cannot enable New UI after clean installing Office 365 Pro Plus #291
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Microsoft-Activation-Scripts#291
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Dusk-Golem on GitHub (Apr 9, 2024).
Original GitHub issue: https://github.com/massgravel/Microsoft-Activation-Scripts/issues/420
Hi there, yesterday I clean installed windows 10 Iot Enterprise v19045.4170 and installed Office 365 Pro Plus v16.0.17425.20146 (even though today is Patch Tuesday 🙃 ) using the OfficeRTool and after activating using MAS 2.5, I can't seem to activate the new visual ui no matter how many times I restart the office apps. I have tried scrubbing and reinstalling but still no luck. Also, the megaphone icon (from where you can open the coming soon panel and activate the New UI) on top right of the screen of the office app (word, excel and powerpoint) does not appear for me no matter what. Can you guys kindly look into it?
I will also try updating the office to the latest version (April's patch tuesday update) to see if that solves it. If its does, I'll mention it here.
@xfqwdsj commented on GitHub (Apr 20, 2024):
I have the same problem on 17602.20000. Have tried several times to open the application, use it for a while and then close it. Windows 11 Workstation 22631.3447.
@xfqwdsj commented on GitHub (Apr 20, 2024):
Sorry, forgot to mention that. These registry entries are all added.
@xfqwdsj commented on GitHub (Apr 22, 2024):
OK, I will try on weekend.
@Dusk-Golem commented on GitHub (Apr 23, 2024):
Sorry for the late reply. Using the registry key worked for me.
@ACRavelo commented on GitHub (Apr 23, 2024):
Devs are being shuffled.
@xfqwdsj commented on GitHub (Apr 26, 2024):
This works, thanks!
Please close this issue.