Open Command Prompt and run bellow command. and reboot the computer or go to task manager and restart “windows explorer” process

To Get Old Context Menu:

reg.exe add “HKCU\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\InprocServer32” /f /ve

If you need to get back the New Context Menu:

reg.exe delete “HKCU\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}” /f

UPDATE 2023-November

HUGE GROUND BREAKING DISCOVERY! To ALL users that don’t meet the artificial requirements for Windows 11, I GOT SOME GREAT NEWS TO SHARE! When adding “/product server” switch to setup.exe in the Windows 11 setup directory, it BYPASSES the Windows 11 hardware requirement checks.

Method: Modify Registry

This method involves simply editing Windows Registry during the installation process of the new operating system. On unsupported devices, if you try to install the new OS, a message will appear on your screen stating that the computer isn’t compatible.

At that screen, you need to press Shift+F10 to open Command Prompt window and modify the registry. In Command Prompt, you need to run regedit.exe and create a new key “LabConfig” under HKEY_LOCAL_MACHINE\SYSTEM\Setup. In the “LabConfig” key, create two new entries:

• BypassTPMCheck=dword:00000001
• BypassSecureBootCheck=dword:00000001

Save the changes and compatibility errors will disappear.

Update | 2021 – October – 06

The fix itself is fairly straightforward too. Simply hit Win+r and type regedit to bring up the registry editor. Make your way to HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup and then right-click the main panel and create a new DWORD (32-bit) Value with a name of AllowUpgradesWithUnsupportedTPMOrCPU and set its value to 1. 

Windows 10 updates tend to break things, and the most recent Window 10 version 2004 update is no exception. According to numerous forum posts, the latest irksome bug prevents Windows 10 apps from accessing the internet even when the PC is successfully connected and your web browser is working just fine.

Microsoft acknowledged this bug in a support forum thread and says it stems from an issue with Windows 10’s Network Connectivity Status Indicator. The company is investigating and will patch the problem it once a solution is engineered, but some users have already found a reliable workaround that should restore network connection for your apps in the meantime.

How to fix the Windows 10 version 2004 network connectivity bug

1. Search for “Registry Editor” using the search bar in the Windows taskbar
2. Open Registry Editor from the search results and click “Yes” when prompted to let the app make changes.
3. In the Registry Editor app, go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters\Internet
4. Right-click “EnableActiveProbing” and select Modify.
5. Change the “Value data” from 0 to 1.
6. Click “OK” to close the window and save your edits.
7. Close the Registry Editor.
8. Restart your computer for the changes to take effect.

With luck, your apps will be able to connect to the internet again once you reboot your PC. If they don’t, double-check you input that registry fix properly. If you’re still out of luck, you might have to seek out a different solution or wait for Microsoft’s patch. If you happen to have encounter another fix or discovered your own

Source | Lifehacker.com By Brendan Hesse

Some Windows 10 users with May 2019 update are seeing a new partition called PortableBaseLayer. If this is your first time, you might wonder what in the world is the PortableBaseLayer partition.

What is PortableBaseLayer Partition?

Before you ask me, no, PortableBaseLayer is not a virus, malware, or rouge partition.

PortableBaseLayer is a system partition created for Windows Sandbox.

When you enable the Windows Sandbox, the operating system will automatically create the PortableBaseLayer partition and places all the important files that are necessary to run the sandbox.

Depending on your usage, the partition size will be anywhere from 1GB to 10GB. Sometimes, it might even exceed that range too.

In case you don’t know, Windows Sandbox is what it sounds like. It is a built-in sandbox that lets you test programs and settings without affecting the host operating system. Compared to traditional solutions like VMware and VirtualBox, Windows Sandbox is lightweight, fast, and easy to use.

How to disable Sign-in screen blur background using Settings

The easiest and safest process to disable the acrylic material effect in the Sign-in screen background is to use the Settings app, with these steps:

1. Open Settings.
2. Click on Personalization.
3. Click on Colors.
4. Turn off the Transparency effects toggle switch.

Once you complete these steps, the Sign-in screen will show a clear background like in previous versions. The only caveat to using this option is that you’ll also lose the transparency effects across the desktop and apps.

Read more »

According to Microsoft These are the Requirements for “Game DVR On Windows 10”

for Original Source click Here

But i had all requirements on my Computer and i still get that error and this helped me to fix this issue.

1)Hold windows button and then press R to open RUN.
2)Type “regedit” and press enter
3)Go to HKEY_lOCAL_MACHINE/ SYSTEM/ CurrentControlSet/ Control
4)Change the entry PortableOperatingSystem from 1 to 0.
5) Reboot

Just to share my 3-day battle with Windows 7 32bit Pro after it was installed on the Kingston V+100E Self-encrypting SSD 64GB.

To be fair, the problem has little to do with the Kingston SSD actually. There may be incompatibility with Truecrypt 7.1 & Self-encrypting SSD, or it could be old registry entries left-over from my old encrypted HDD but I didn’t investigate further since I’ve solved my hibernation problem.

Update at the end of this article!

*******************************

System:

OS: Win7 32bit Pro (New install, not upgrade)

Laptop: Fujitsu T4215 with CPU upgraded to Intel T7200

HDD: WD Scorpio Black 320GB (Truecrypt 7.1 System FDE) -> Kingston V+100E 64GB (Self-encryption)

Drivers: (All updated to latest from manufacturer)

********************************

Everything seems to work well until I run Easy Transfer to transfer my account from my old HDD to the new SSD. My old WD Scorpio Black was encrypted using Truecrypt 7.1 so there were active Truecrypt registry entries which I’m not aware of & few people seem to know about. Google it & you would’t find many entries if any.

Hibernation will always fail with black screen. When KB/Mouse is touched, the login screen is shown. Event Viewer will show Event ID 45 Error caused by volmgr on \device\harddiskvolume2 (which is my C:\). What’s cryptic is the error is a crash dump driver error. What has crash-dumping in volmgr.sys got to do with hibernation?

A lot in fact, after kernel-mode drivers had crashed or unloaded, the only way the NT Kernel could do stuff is through special filters apparently. So to activate Hibernation, the Kernel has to unload everything & dump everything in RAM to HDD. What if you’re running Bitlocker or Truecrypt, which are software-based encryption?

The Kernel has to filter the RAM data thru these small programs so the Hibernation or Crash dumps are encrypted as well, else there’ll be a security risk. dumpfve.sys for Bitlocker & truecrypt.sys for Truecrypt 7. Unfortuntately I don’t see this documented anywhere. (I did not search SourceForge though.) I found out when I was hunting in the registry.

This registry key is where I found the offending entry.

HKLM\SYSTEM\CurrentControlSet\Control\CrashControl -> DumpFilters

In it, I found “dumpfve.sys” & “truecrypt.sys”. Now I did not install Truecrypt in the new system so the only way is thru’ Easy Transfer.

OK, fine, so I install Truecrypt 7.1 to make sure the proper files are installed. But after rebooting, Windows BSOD & I couldn’t see any crash dump! It may be that active Truecrypt registry is still there thinking the SSD was encrypted. Well I can’t have that! So I did a System Restore & booted up. I then remove the truecrypt.sys entry in all Registry keys, adjust my pagefile size, enabled crash dump 128KB & enabled hibernation with “-size 100”.

Hit the Hibernation button & it WORKS!!!

After that, whatever changes I did to pagefile.sys & crash dump size did not affect Hibernation.

So for those of you who have hibernation problems with Event ID 45 from volmgr. Check your crashdump filter.

Now I still need Truecrypt to access the old encrypted WD Scorpio Black, so what I did was to install Truecrypt in “Portable” mode & run the .exe files instead of an installation. Done!

Update (19/3/2012):

Recently I cleaned the registry of all entries with Truecrypt & install the latest 7.1a version & Windows did not BSOD so I’m a happy camper again. Seems like Truecrypt doesn’t leave many entries in Windows itself, which is a GOOD thing!

Thanks to Eric Tay (original source)

First Make Sure your not having a OEM or Retail Version installed, before activate with a MAK Key

Run this command to find the Edition installed

slmgr -dli

Below are some commands that can be used to convert a Windows 7/8/10 machine from KMS licensing over to MAK by using a MAK key:

1. Open an administrative command prompt (or run a remote psexec shell or remote PowerShell).
2. Change directory to C:\Windows\System32
3. Run the following command to uninstall the current product key on the system:

   cscript slmgr.vbs /upk

4. Install the new MAK key using the following command:

   cscript slmgr.vbs /ipk TypeYourMAKkeyHereWith-

5. Once the new key is installed, activate it using the following command:

   cscript slmgr.vbs /ato

6. You can check the licensing status using the following command:

   cscript slmgr.vbs /dlv

1.       Open a command prompt, type in Diskpart and then press Enter.

2.       Run the command “List Disk” and press Enter.

 

3.       Decide which disk you want to look at and then run the command “Select Disk n” where n stands for the number you see from the previous command.  In this case, I am going to look at disk 2.

 

4.       To see the attributes of Disk 1 now that it is selected, run the command “attributes disk”.

 

5.       To clear the “Read-only” attribute, run the command “attributes disk clear readonly”.