Fix Microsoft 365 Installation Failure After Moving Windows to SSD
Question details
The user is experiencing repeated failures when trying to install or repair Microsoft 365 after migrating Windows and personal files to a new SSD.

- Product
- Microsoft 365
- Device & OS
- Windows
- Scenario
- Installing or repairing Microsoft 365 after migrating the OS and files to a new Solid State Drive (SSD), specifically with a school subscription account.
- Observed behavior
- The installation fails, errors occur during the Office Deployment Tool process, or Office installs but immediately requests a repair and crashes.
Ensure your Windows operating system is fully updated to the latest version and temporarily disable any third-party antivirus software that might be interfering with the Microsoft 365 installer.
Create a New Local Administrator Account
User profile corruption or permission issues caused by manual file transfers can block Office installations. Creating a fresh administrator account bypasses these system conflicts.
When files are manually transferred from an old drive to a new SSD, existing user profiles can suffer from broken registry links or missing permissions. Installing Office from a completely new local administrator account isolates the installation from these profile-specific errors.
Click the Start button, select the gear icon to open Settings, and navigate to 'Accounts' > 'Other users' (or 'Family & other users').
Click 'Add account'. On the prompt, select 'I don't have this person's sign-in information', followed by 'Add a user without a Microsoft account'. Enter a username and password.
Once the account is created, click on it in the list and select 'Change account type'. Change it from 'Standard User' to 'Administrator' and click OK.
Sign out of your current Windows profile, log into the new administrator account, and run the Microsoft 365 installer again. Once installed, sign in to any Office app using the school account associated with your subscription to activate it.

Verify Windows Installation and Integrity
Checking the OS installation method helps identify underlying system file conflicts that prevent Microsoft 365 from installing correctly.
Use WPS Office When Microsoft 365 Won't Install
If Microsoft 365 continues to crash or fail after your SSD upgrade, WPS Office provides a lightweight, highly compatible alternative that installs quickly without complex system dependencies or profile conflicts.
- 1. Download the Installer: Visit the official WPS Office website and click 'Download' to get the lightweight installation file.
- 2. Install WPS Office: Run the downloaded file. The installation process is quick and bypasses the complex system requirements that often cause Microsoft 365 to fail.
- 3. Open Your Existing Documents: Launch WPS Office and directly open your existing Word, Excel, or PowerPoint files without losing any formatting.

Frequently Asked Questions
Why does Microsoft 365 crash immediately after installing on a new SSD?
This often happens due to corrupted user profiles, leftover registry keys from a previous installation, or permission issues caused by manually copying program files from an old drive to the new SSD instead of doing a clean installation.
Can I use my school account to activate Microsoft 365 on a personal Windows profile?
Yes, you can install Office on your personal Windows local user account. When you launch applications like Word or Excel for the first time, you simply sign in with your school credentials to activate the software without converting your entire Windows login.
Does cloning an SSD cause Microsoft Office license issues?
Cloning a drive can sometimes trigger hardware ID changes that invalidate your Office activation or corrupt the installation files, requiring you to use the Office Deployment Tool or Support and Recovery Assistant to completely reinstall and reactivate the software.
What should I do if the Office Deployment Tool also fails?
If both the standard installer and the Office Deployment Tool fail, creating a new local administrator account via Windows Settings and running the installer from there is the most effective way to bypass system-level permission blockers.




