Windows 10: Microsoft Store Won't Open After Cloning OS to New SSD

I got a new M.2 SSD and cloned my C drive to the new SSD and after rebooting, all Microsoft Store apps are greyed out including the Microsoft Store itself.

I have already updated Windows and did a reset by running wsreset.exe. This page suggests to report a problem through the Feedback Hub but I am unable to access the app because it runs off of a Microsoft Store application.


Thanks.

:)

 

Moving to SSD. Clone or not to clone?

I kinda agree with you, but on a wholr, do not. While I have done things a bit differently than this specific situation, by installing Windows directly to the SSD, and cloning after, my testing shows that there are no issues doing this, very little that can go wrong, provided your system is stable.

There are certain features that must be disabled in this situation, like auto defrag and such, but even with a fresh install to the SSD, you need to take steps to ensure that you SSD performs properly, regardless of how the data got there.

Arming yourself with a bit of knowledge can go a long way.

Installing the latest chipset driver, and the RST Tools, will ensure optimal performance of the SSD. but rather than taking my advice, I suggest the OP takes a look here:

http://blogs.dirteam.com/blogs/sand...7-and-ssds-to-clone-windows-or-reinstall.aspx

Installing The SSD - Install A Solid State Drive In Your Notebook | Tom's Hardware

Keep in mind, also, Digibucc, that many retail drives include software and such that very specifically is to be used to ttranser the OS from an existing mechanical drive to an SSD, and if there really was alot fo issues stemming from the cloning process, they would not have packages like that, simply to eliminate tech support costs. While not the optimal option, cloning is NOT a bad thing, as long as you take the nessecary steps.

 

Unable to Boot to Windows 10 after Cloning old SSD to new SSD

I use AOEMI free . They use the term 'migrate' OS to new SSD (but it will also migrate\clone to HDD or HDD to SSD).

Ah! Yes, I overlooked the NVMe part of your SSD description. This does rule out any swapping of ports, unfortunately,

but the recent versions of the cloning programs should normally write a boot sector to your new SSD.

You could still connect the HDD to an internal SATA port rather than using USB though... or not ?

- The main difference between an Image and Clone is the clone is an exact replica of your C:\ drive including fragments and

unused space. With an SSD the fragments don't much matter, and when I clone to an HDD I always do a full de-fragment and optimise

(optimising moves files that may be spread out on the HDD into a contiguous order) after doing the clone, but this is

more about performance on the HDD than the final result on the SSD should I need to clone back to an SSD at some point.

(I make a new clone on a HDD prior to every Win10 version update as a precaution should the update bork my OS).

btw - The base of my Win10 is Win7 installed in Jan 2010 which has been cloned to two new machines (using new license keys)

prior to upgrading to Win10.

Still performs as well as a clean install of Win10 I did as a test (and never used because, even after spending half a day installing and getting

the basics sorted out, I would have still needed a lot more time dealing with a lot of games and software).

.

 

Windows 10 deactivated on new cloned SSD

Well it would appear the issue was solved!

What I did was re-insert and boot the original SSD went into Settings

Selected Accounts

Clicked on Manage my Microsoft account, got a message stating the account needed to be updated

After that was done, I cloned the new SSD again

On the cloned SSD entered command prompt, used the slmgr with my product key command (was entered successfully)

Then used the slmgr /ato command...and voila, Windows was reactivated successfully!

So thank you all for the possible solutions you suggested. I will keep monitoring the system as time goes by.