For me since Build 17666 I’ve had to use Powershell commands to be able to launch the MSFT Store app. Many threads in Feedback about this, and I’ve upvoted a few.
Conversation
4 comments
NoFlames
04 January, 2019 - 7:02 pm
<p>There surely must be a fix for this? I haven't personally had that problem, but I try to jump on the insider build close to the end of the dev cycle when they are done with features and deep into bug fix mode.</p><p><br></p><p>My biggest complaint is when they break things that seem obvious like what you mentioned. But normally they fix it in the next build if it's critical.</p>
<p><a href="https://www.thurrott.com/forums/microsoft/microsoft/thread/windows-10-insider-builds-whats-your-biggest-annoyance#391576" target="_blank"><em>In reply to NoFlames:</em></a></p><p>Many of the Feedback complaints about this go back a year. I'd guess this is specific to systems with specific and unusual configurations. In my case, a VM (I'd never run Insider Builds outside a VM) with a 40GB VHD plus a 32GB VHD it shares with other Windows VMs on which I put all my portable software.</p>
<blockquote><a href="#391603"><em>In reply to hrlngrv:</em></a><em> Now that you mention it running in a VM that does ring a bell. I've had Windows Server VM running on Hyper-V server where Windows update wouldn't work and could never figure it out. Other Windows Server VM's didn't have the problem. So it sounds like something like that for you but with the store.</em></blockquote><p><br></p>