Fix the Administrative Privileges Required Error When Installing Microsoft Office 2016
Question details
The user needs to install Microsoft Office 2016 on a Windows 10 laptop while upgrading from Office 2010, but the installer requests administrative privileges.

- Product
- Microsoft Office 2016
- Device & OS
- Windows 10 laptop
- Scenario
- Upgrading from Office 2010 to Office 2016 using the laptop's only administrator account.
- Observed behavior
- Installation fails with an Administrative Privileges Required message even though the signed-in user is an administrator.
Confirm that the Office 2016 installer came from Microsoft or your institution's authorized software portal. Have your Windows administrator credentials available, and close any open Office applications before retrying installation.
Verify the installer and run Office setup as administrator
Use this first when Office setup requests administrative privileges despite your account being an administrator.
Membership in the Administrators group does not mean every application automatically runs with elevated permissions. Starting setup with Run as administrator explicitly requests elevation.
Locate the downloaded Office setup file in File Explorer and confirm where you obtained it. If the source is unknown or unofficial, obtain a fresh installer from Microsoft or your institution's authorized software portal instead.
Open Start > Settings > Accounts > Your info and check whether Administrator appears under your account name. If it is a standard account, you will need credentials for an authorized administrator account.
For an executable installer, right-click the Office setup .exe file in File Explorer and select Run as administrator. Approve the User Account Control prompt, or enter administrator credentials when requested, then follow the setup prompts.

Retry Office installation from a new local administrator profile
Use a fresh Windows profile if a verified installer still reports missing privileges after you run it as administrator.
Work with Office documents while resolving the installation error
WPS Office is a free, lightweight alternative with a familiar interface and support for common Microsoft Office formats, making migration straightforward. It lets you work on documents, spreadsheets, and presentations without relying on the Office 2016 installation, but it does not repair Microsoft's installer or bypass Windows permissions.

Frequently Asked Questions
Why does Office setup ask for administrative privileges when I am already an administrator?
Windows normally runs applications without elevated permissions, even for administrator accounts. Right-click the Office setup executable and select Run as administrator to request elevation, then approve the User Account Control prompt.
What should I do if Run as administrator is not available?
In File Explorer, check that you are selecting the actual setup .exe file rather than a shortcut, folder, or other installer package. If your institution supplied a different installation method, follow its instructions or ask its IT team how to launch setup with the required permissions.
Will creating a new Windows account remove Office 2010 or my files?
Creating an account through Settings > Accounts > Family & other users does not itself uninstall Office 2010 or delete files in your existing profile. The new account has a separate profile, so your desktop, settings, and personal files will not automatically appear there.
Can a new administrator profile bypass my institution's installation restrictions?
No. A new profile may help isolate an account-specific problem, but it does not override device-wide security policies. If installation or administrator approval is blocked on a managed laptop, contact your institution's IT team.
Can WPS Office fix the Office 2016 administrative privileges error?
No. WPS Office is an alternative for opening and editing Office-format files, not a repair tool for Microsoft's installer. Its own installation must also follow your device's Windows permissions and organizational policies.




