[GH-ISSUE #235] office 2016 pro plus converted to 2019 pro plus. #169

Closed
opened 2026-02-27 10:09:58 +03:00 by kerem · 2 comments
Owner

Originally created by @Stofa14 on GitHub (Jul 24, 2023).
Original GitHub issue: https://github.com/massgravel/Microsoft-Activation-Scripts/issues/235

After activation using method 1 (powershell), my office 2016 pro plus converted to 2019 pro plus.

Originally created by @Stofa14 on GitHub (Jul 24, 2023). Original GitHub issue: https://github.com/massgravel/Microsoft-Activation-Scripts/issues/235 After activation using method 1 (powershell), my office 2016 pro plus converted to 2019 pro plus.
kerem closed this issue 2026-02-27 10:09:58 +03:00
Author
Owner

@thecatontheceiling commented on GitHub (Jul 24, 2023):

it wasn't converted to 2019, that is just the license name. it's still 2016

<!-- gh-comment-id:1647717025 --> @thecatontheceiling commented on GitHub (Jul 24, 2023): it wasn't converted to 2019, that is just the license name. it's still 2016
Author
Owner

@antoni0C0des commented on GitHub (Jul 26, 2023):

Isn't that better tho?

<!-- gh-comment-id:1651522089 --> @antoni0C0des commented on GitHub (Jul 26, 2023): Isn't that better tho?
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Microsoft-Activation-Scripts#169
No description provided.