Windows 10: Microsoft Window 11 Home Problem

I just got a new gaming desktop few days ago, it came with window 11 home version. The problem I have is I don't know how to use it properly please help me. Some of the apps are not even in it Window 11Like opening up paint or notepad instead using Window key + R to run it is terrible. They should give us the option like window 10, right click on desktop > new > notepad or paint.How do I open up Microsoft Store App? whenever I type in search bar the name "Microsoft Store" or "Microsoft Store App" from the taskbar to install applications. It never shows up or pop up the "Microsoft Store"

:)

 

Nvidia driver problem with 940 MX on Windows 10 x64

I would only go back to the driver from the computers manufacturers if you experience any issues with the latest drivers from devie manufacturers.

If everything is still working well with the clean boot then you can start troubleshooting as follows to start:

How to determine what is causing the problem after you do a clean boot


1. Log on to the computer by using an account that has administrator rights.
2. From Start, search for msconfig. (In Windows 10, use the Search box from the Start menu. In Windows 8 or 8.1, swipe in from the right edge of the screen, and then tap Search. Or, if you are using a mouse, point to the lower-right corner of the screen, and then click Search.)
3. Select msconfig or System Configuration from the search results.
4. Tap or click the Services tab, and then tap or click to select the Hide all Microsoft services check box.
5. Tap or click to select the upper half of the check boxes in the Service list.
6. Tap or click OK, and then tap or click Restart.
7. After the computer finishes restarting, determine whether the problem still occurs.
• If the problem still occurs, repeat steps 1 through 6, but clear the lower half of the check boxes in the Service list that you originally selected.
• If the problem does not occur, repeat steps 1 through 6, and select only the upper half of the remaining check boxes that are cleared in the Service list. Repeat these steps until you have selected all the check boxes.
• If you still experience the problem when only one service is selected in the Service list, this means that the selected service causes the problem, and you should go to step 11. If no service causes the problem, go to step 8.
8. Repeat steps 1 and 3 in this section.
9. Tap or click the Startup tab, and then tap or click to select the upper half of the check boxes in the Startup Item list.
10. Click OK, and then click Restart.
• If the problem still occurs, repeat steps 8 and 9, but clear the lower half of the checked boxes in the Startup Item list that you originally selected.
• If the problem does not occur, repeat steps 8 and 9, and select only the upper half of the remaining check boxes that are cleared in the Startup Item list. Repeat these steps until you have selected all the check boxes.
• If you still experience the problem after only one Startup Item is selected in the Startup Item list, this means that the selected Startup Item causes the problem, and you should go to step 11. If no Startup Item causes this problem, a Microsoft service probably causes the problem. To determine which Microsoft service may be causing the problem, repeat steps 1 through 7 without selecting the Hide all Microsoft services check box in each step.
11. After you determine the startup item or the service that causes the problem, contact the program manufacturer to determine whether the problem can be resolved. Or, run the System Configuration utility, and then tap or click to clear the check box for the problem item.
From <https://support.microsoft.com/en-us/help/929135/how-to-perform-a-clean-boot-in-windows>

 

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

 

Windows 10 1709 System Restore problems...

That seems to be an attempt at Option 2 in the tutorial, which requires you to
a. Boot to a command prompt (Did you?)
b. You then seem to be mixing steps 3,4 and 5, thus your command is incorrect.

I suggest Option 1 is easier.

If you still have problems, please repost listing each specific step and saying which option from the tutorial you are using. Thanks.