Windows 10: Some Microsoft Apps not working after Windows Update

So a few weeks ago when I started my computer, there was a pop-up saying Cortana was updating something like that. I was using a Local Administrator Account But also some other Microsoft apps weren't working! Like MS Store, Photos, Clock, Feedback Hub and a few others. I logged into a Microsoft account and updated to the latest Windows, but that still didn't fix the problem. I even tried some other stuff I found on Google, but no luck. Please help me...

:)

 

Windows 10 KB3213986 Update Cripples Multi-monitor Gaming

This should be enough to get the conspiracy theorists suggesting that Microsoft is intentionally crippling multi-monitor support in fullscreen mode since games sold on the Microsoft Store all work in the pseudo-fullscreen mode...

Or it could just be an idiotic bug that will be fixed in time.

 

Microsoft Apps are not working

Hi,

Thank you for posting your query in Microsoft Community. We understand the inconvenience caused and will assist you.

I suggest you to run the Windows Store Apps Troubleshooter by following the steps below:

• Type “Troubleshooting” in search bar and press Enter.
• Click on “View All” on top left pane.
• Select “Windows Store Apps” from the list and follow the prompts for troubleshooting.

Also, I suggest you to check if there are any updates available for the apps in Windows Store.

If the issue still persists, suggest you to create another user account and check for status.

Create a local user account in Windows 10

Create a local user or administrator account in Windows

Hope this helps. Keep us posted on the status for further assistance.

 

Microsoft Botches Up UEFI Support for Windows 7 on ASUS Motherboards



Microsoft suggests updating to Windows 10 to patch Windows 7

• 
  
  
• Chris Merriman
• 
  @ChrisTheDJ
• 05 May 2016

• Tweet
• Facebook
• Google plus
• Send to

9 Comments

MICROSOFT HAS confirmed a potentially lappy-borking problem that it won't be fixing, because Windows 7.

Woody Leonhard, the respected Windows columnist, points to a problem involving Asus motherboards, which also appear rebadged in a variety of other manufacturers' machines, and the activation of UEFI Secure Boot for Windows 7 in a patch KB3133977.

Short version: install update, welcome to Borksville, population you.

Both Asus and Microsoft acknowledged the problem. Microsoft entitled the article "BitLocker can't encrypt drives because of service crashes in svchost.exe process in Windows 7 or Windows Server 2008 R2", but we prefer to just call it "Trevor for brevity."

The firm's advice was that it's an optional update, leave well alone, you'll be fine, or alternatively turn secure boot off.

Then Microsoft did a silly, silly thing.

It moved the update from 'optional' to 'recommended' and anyone who reads this site regularly will know what happens when Microsoft does this. That's right boys and girls - it makes it automatically install, unless you've specifically told your machine not to.

So now, if you have one of the affected motherboard and you keep your security updates automatic like wot Microsoft recommends, then your machine will stop working properly.

We should add it's not permanently bricked, but it will take some mucking about in the BIOS to fix and that's a pain even for an experienced computer user.

Microsoft has, by offering a workaround, suggested heavily that it won't be fixing the problem, though we have asked the question, so expect a response in about a fortnight.

But the real kicker is this piece of advice: "Note The Secure Boot feature is supported in Windows 10. To learn more about the security advantages of this feature and about the upgrade path from Windows 7 to Windows 10, go to the following Windows website"

Holy toledo, this company really knows how to rub people up the wrong way.

After all - if the advice is to manually avoid the update or move to a version of the operating system where there's virtually no control over updates, then Microsoft is dealing in massive contradictions.

A more cynical site would suggest that it's yet another example of Microsoft running Windows 7 into the ground and adding built in obsolescence to encourage quicker updates. But we're not that sort of site.

Its the patching to force secure boot that is the problem win 7 does not support secure boot
hence it borks systems and well microsofts answer is Cactus >your Asshole > insert

from the inquirer