Windows 10: Escape Microsoft Window

I cant get out of microsoft window. Tried restarting several times and opens with that window. There is no X to escape,

:)

 

Trouble with Farmville Country Escape app

Hello,

Thank you for posting in Microsoft Community, we appreciate your interest in Windows 10.

I apologize for the inconvenience caused to you with playing the game Farmville 2 Country Escape as it crashes, we will help you with this issue.

This behavior can be caused due to conflict between build-in and purchased app or any other third party software. Hence, I would suggest you to try the methods below and check.

Method 1: As an initial step, I would suggest you to follow the below steps and see if the issue can be resolved.

• • • Type Troubleshooting in the search next to start on the desktop and select
      Troubleshooting.
    • Click on View All on left side and select Windows Store Apps.
    • Click on “Advanced” and then click on “Run as Administrator”
    • Click “Next” and follow the on-screen instructions to complete the troubleshooting process.

Method 2: If the issue still persists, try to uninstall the game and re-install it from the
Windows Store and check.

Uninstall the game:

• Type Programs in the Search box from the desktop and select
  Programs and Features.
• Right click on Farmville 2 Country Escape and click on
  Uninstall.
• Later try to install it from the Windows Store.

Also refer to: For Help with Gaming Issues

Hope it helps. Kindly update the status of this issue, we will be happy to help you.

 

windows xp installation and dual core am

could someone please list the steps they follow to install windows with a dual core processor and windows xp service pack to. I'm reletively new to amd dual core and i feel i'm missing a step. All help will be appreciated. thanx

 

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