Task View feature inside Windows 11 is actually a great feature, letting you quickly view open windows and virtual desktops. How Task view itself could be reached with keyboard shortcut combination of ⊞ WINDOWS + TAB some users will prefer this way of using it and thus button on the taskbar is something you do not want or need.
There is a very easy way to remove mentioned button and I will show you how to do it.
Right-click the taskbar button itself and click on Hide From Taskbar.
That’s it, you have done it.
Now in order for you to bring it back if you change your mind, you will have to do some extra steps but it is nothing difficult.
Right-click on the taskbar and click on Taskbar settings, you will be lead to Personalization > Taskbar.
Inside locate Taskbar Items and switch Task View to ON, you will see the Task View button right away showing itself again.
If you are trying to copy a folder or a file but encountered an error that says, “An unexpected error is keeping you from copying the folder. If you continue to receive this error, you can use the error code to search for help with this problem”, read on as this post will guide you on how you can fix this error.
This kind of error is a CHKDSK error. It is the “Volume is dirty” error message with error code 0x80071AC3 which indicates that the CHKDSK operation on your computer did not go through due to some corrupted sector of your hard drive, data corruption, corrupted system files, malware infection, as well as improper installation of an application that left some residual folders and files and many more.
To fix the Error 0x80071AC3, here are some potential fixes you can check out to resolve it:
Option 1 – Run the Check Disk utility
You can also run the Check Disk utility to fix the error when you connect your USB or external device.
In the Windows Search box, type “command prompt” and from the search results, right-click on Command Prompt and select “Run as administrator”.
After opening Command Prompt, type this command and tap Enter: chkdsk /r /f <PARTITION LETTER>
The command you entered will start to check for errors and fix them automatically. Else, it will throw an error message saying, “Chkdsk cannot run because the volume is in use by another process. Would you like the schedule this volume to be checked the next time the system restarts? (Y/N)”.
Tap the Y key to schedule Disk Check the next time your computer restarts.
Option 2 – Try to check if a particular volume is dirty and exclude it
The next thing you can do to fix the problem is to check if the particular volume is dirty and exclude it. To do so, follow these steps:
In the Start Search, type “command prompt” in the field and right-click on Command Prompt from the search results, and then select the “Run as administrator” option.
After opening Command Prompt with admin privileges, execute this command: fsutil dirty query <PARTITION LETTER>
After that, you will see either of the following results of the command you just executed:
“Volume <PARTITION LETTER> is dirty”
“Volume <PARTITION LETTER> is not dirty”
If you see the “Volume <PARTITION LETTER> is dirty” message, then you can just skip checking the drive for errors by executing this command: CHKNTFS /X <PARTITION LETTER>
Option 3 – Try to format the destination drive
If the first two options above didn’t work, then you might want to try formatting the drive can also help you resolve the error. To format it, follow these steps:
To get started formatting your drive, tap the Win + E keys and then go to the access page of the drive.
Next, right-click on the drive and select Format.
After that, uncheck the “Quick Format” option and then format your drive properly.
Now once the formatting process is finished, unplug the drive and plug it back in afterward.
Check if the error is already fixed. If the drive is not initialized, tap the Win + R keys and hit Enter.
After opening the Run dialog box, type “diskmgmt.msc” and hit Enter to open Disk Management.
From there, right-click on the drive volume and select initialize disk.
Next, select the correct partition type and proceed.
Interrupts are designed so that the resource requests don’t get into a headlock when it comes to the hardware level. To simply put it, it is used to break a loop that never ends. Aside from that, developers also designed levels in order to prioritize interrupts. It is also known as “Interrupt Request Level” or IRQL. And if you suddenly encounter a “Bugcode 0xA –IRQL_NOT_LESS_OR_EQUAL” error, this means that a driver has accessed a memory location illegally while NT is operating at a specific IRQL.
The Bugcode 0xA –IRQL_NOT_LESS_OR_EQUAL is a fatal driver coding error and as an end-user, there isn’t much that you can do to resolve it but if you’re a developer, then this means that your code is trying to access an invalid memory location. You could check on different parameters such as memory location that was referenced and code addressed which referenced memory. The technical parameters are:
a memory location that was referenced
IRQL at time of reference
0 = read, 1 = write
code addressed which referenced memory
As mentioned earlier, if you are an end-user, there is nothing much that you can do to resolve this problem, but worry not for there are still possible solutions that could help you in fixing it. Refer to the suggestions laid out below to fix Bugcode 0xA –IRQL_NOT_LESS_OR_EQUAL error.
Option 1 – Try running the Hardware and Devices Troubleshooter
The first thing you can do to fix the problem is by running the Hardware Troubleshooter. Although it won’t make much of a difference, there’s still a possibility that it could automatically fix the problem. To use it, refer to these steps:
The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
After opening Settings, look for the Update and Security option and select it.
From there, go to the Troubleshoot option located on the left-hand side of the list.
Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.
Option 2 – Try to update or rollback your device drivers
If the first option didn’t work for you, then it’s time to either update or roll back the device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.
Open the Devices Manager from the Win X Menu.
Then locate the device drivers and right-click on them to open the Properties.
After that, switch to the Driver tab and click on the Uninstall Device button.
Follow the screen option to completely uninstall it.
Finally, restart your computer. It will just reinstall the device drivers automatically.
Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.
Option 3 – Run the Memory Diagnostic Tool to check for Memory leaks
Tap the Win + R keys to open Run and type exe and hit Enter to open the Windows Memory Diagnostic Tool.
After that, it will give two options such as:
Restart now and check for problems (Recommended)
Check for problems the next time I start my computer
Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.
Note: After you select the option, your PC will restart and check for memory-based issues. If it finds any issues, it will automatically fix them and if there’s no issue found, then it’s most likely not a memory-based issue so you should try the other options given below.
TPM 2.0 requirement for Windows 11 has produced a lot of discussions since it was announced. A lot of somewhat older hardware seems to be left behind with this decision from Microsoft.
So naturally, when something like this is announced, especially when it is stated it is the must-have thing, people find a way to break it and to prove it is not the case.
In that spirit, I am proud to present you with not one but three-way you can install Windows 11 on hardware that does not has TPM 2.0. Please note that by bypassing this you will not be able to use some Windows 11 features tied to modules like Device encryption, vTPM in Hyper-V, and all TPM-related services.
I will cover methods from the most simple and straightforward ones to the more complicated using registry editor.
Bypass TPM with changing installation media
For this method to work you will need both Windows 10 ISO and Windows 11 ISO since it will require some file copying between them.
You will also need Rufus or another tool to make a new installation media once files are copied
All you have to do in this method is to go into your Windows 10 ISO and delete the install.esd, then just copy install.wim from Windows 11 installation media into the same place, and you are done.
Make install ISO with Rufus and install Windows 11.
Change DLL on installation media method
For this method, you will need everything like in the previous one and the process is almost the same, but this time instead of migrating the whole installation file, we will just replace the appraiserres.dll file.
Copy appraiserres.dll file from your Windows 10 installation media over the same file on Windows 11 installation and you are good to go.
Bypassing TPM via registry editor
If for some reason previous easy solutions have not worked for you do not lose hope just yet, there is one more way you can bypass TPM.
In this given method you will not need Windows 10 installation media but the process is a little more complicated than previous ones.
Create Windows 11 media installation
Start the installation process
Click the Next button.
Select region, language, and time when asked. You can change these settings later.
Click the Install now button.
If your device was already activated, click the I don’t have a product key option to continue.
Click the Next button.
Select the edition of Windows. When you’re installing the OS on an existing device, Windows won’t activate if you select the incorrect edition.
Click the Next button.
Select the I accept the license terms option and click next.
Select Custom: Install Windows only (Advanced)
During the Windows installation screen, now you will see a message stating that the PC can’t run Windows 11 if you do not have TPM 2.0
On this screen, press SHIFT + F10 to open Command Prompt window.
Launch the registry editor, type regedit.exe in Command Prompt, and press ENTER
Create a new key “LabConfig” by right-clicking on the Setup key and select New > Key under HKEY_LOCAL_MACHINE\SYSTEM\Setup.
Type LabConfig and press ENTER.
Right-click on the LabConfig key.
Select New > DWORD (32-bit) value.
Create two values: BypassTPMCheck and BypassSecureBootCheck.
Set their DWORD32 value to 1.
Press ENTER.
Close the Registry Editor.
Type exit in the Command Prompt and press ENTER or close its window.
Press the back button in the Windows installation setup if it still says “This PC can’t run Windows 11”.
Accept the terms & conditions.
Select Custom: Install Windows only (Advanced) option and configure the partition with the current installation.
The Disk Management tool in Windows 10 is a built-in tool that contains a user interface used to manage disk partitions to administrators of the computer. There are lots of instances when you have to change the size of the hard disk partition or reduce the size and so on. This is where the Disk Management tool comes in. It’s useful as the command line interface can be quite confusing and risky for some users. However, there are cases when this tool stops working. A proof of this the reports submitted recently by some Windows 10 users. Based on the reports, the Disk Management does not load or respond. If you are having the same problem, read on as this post will give you some suggestions on what you can do to resolve the problem.
Option 1 – Try restarting the Disk Management Service
Tap the Win + R key combination to open the Run dialog box.
Then type “services.msc” in the field and hit Enter or click OK to open the Windows Services Manager.
Next, scroll down in the service list until you see the Virtual Disk Service. Double click on it to open and then select Automatic.
Click on Apply and OK to save the changes made.
If it hasn’t started yet, you can just click on the Start button to start the Service. The Virtual Disk service provides management services for disk, volumes, file systems as well as storage arrays.
Now save all the changes you’ve made and restart your computer. Then check if you can now use the Disk Management tool without any problem.
Option 2 – Try using the System File Checker scan
System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files that might be causing some issues with the Disk Management tool. To run the SFC command, follow the steps given below.
Boot your PC into Safe Mode.
Tap Win + R to launch Run.
Type in cmd in the field and tap Enter.
After opening Command Prompt, type in sfc /scannow
The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:
Windows Resource Protection did not find any integrity violations.
Windows Resource Protection found corrupt files and successfully repaired them.
Windows Resource Protection found corrupt files but was unable to fix some of them.
Option 3 – Try using the DISM tool
Aside from the System File Checker, the DISM tool can also help you resolve the issue with the Disk Management tool. It helps in restoring the health of your computer.
Open the Command Prompt as admin.
Then type in this command: Dism /Online /Cleanup-Image /RestoreHealth
Do not close the window if the process takes a while as it will probably take a few minutes to finish.
Option 4 – Try using Diskpart and Fsutil
If both the System File Checker and DISM tool didn’t work, you can use command-line tools like diskpart and fsutil. These command-line tools are powerful but you need to be careful especially if you’re not that familiar with using them. However, it’s recommended that you have somebody who knows if you’re really inexperienced with this kind of stuff.
Error code 0x801901F7, also known as “The Server Stumbled” error because it shows a message saying “The Server Stumbled. We all have bad days” is associated with Windows Store. Server Stumbled Error 0x801901F7 is an error related to the MS server. The error occurs due to damaged registry files, malware, virus, and corrupted data. You should fix this error to prevent a system crash or a BSOD error. There are some things you can do to fix it. These are not so complex. So, anyone can try these methods to fix error 0x801901F7.
Common Symptoms for error 0x801901F7:
Problems with Windows startup
System becomes very slow or the system freezes
Blue screen of death appears
Windows fails to start some process due to Stop error code 0x801901f7
Solution
Error Causes
This error is generally caused by corrupt registry files.
Virus infection can cause this problem.
Outdated driver, missing .DLL files may also cause this error.
Microsoft server overload may cause this problem as well.
Incorrect configuration may cause this problem.
Further Information and Manual Repair
To fix error 0x801901f7, there are four methods listed below. Some might work for you and some might not. Please try all of them to fix this error.
Method 1:
Basic method to fix error code 0x801901F7: Resetting Windows Store Cache
Most of the time clearing or resetting the cache helps. It doesn't always work, but you should try this first before moving on to some advanced methods which are mentioned below.
To reset the Windows Store cache please follow the simple steps below
Open RUN by searching or pressing "Windows Key + R"
Type "wsreset.exe" and press Enter or click on OK.
Windows Store will open automatically along with a command prompt.
This will reset Windows Store and you might see it loading as it should.
This method might work but if it fails to solve Error 0x801901F7 then follow the method below.
Method 2:
Advanced method of fixing error code 0x801901F7: Deleting Windows Store database file.
By using this method, you will be deleting the database file for Windows Store. This file is located on your C drive or the drive where you installed your Operating System. Follow the steps below.
Navigate to C:WindowsSoftwareDistributionDataStoreDataStore.edb.
Delete DataStore.edb file from there.
Now Open Windows Store and see if you still get error code 0x801901F7.
The Datastore.edb file that you deleted will be automatically created once you perform Step 3 which is launching Windows Store.
If you still cannot get this error away then Close Windows Store and Reboot your PC then Launch Windows Store Again.
Method 3:
Modifying Windows update properties:
Perform the steps below only if the above-mentioned methods fail. You will be tweaking a few things in the Windows update to see if it helps.
Open Task Manager by right-clicking on Taskbar, then click on Task Manager.
Go to Services Tab. Click on Open Services at the very bottom of the Window.
Now a new window will pop up. Scroll down & find "Windows Update" from the list.
Double click on Windows update to open up its Properties.
Now from the Startup Type drop-down list, select Automatic. Click on Apply, Start, and then Ok.
Now you need to perform just one more step. Reset Windows Store again (Refer to method 1 for Steps). This should fix your Windows Store error that shows The Server Stumbled with 0x801901F7 Error Code.
Method 4:
If the error is due to a problem with a driver, then follow the method below to uninstall the current driver:
Open the Run command and type “sysdm.cpl” in the text box.
Click Enter.
Open the Hardware tab on the system properties dialog box.
Then press on Device Manager.
Double press on Device type and then press on the hardware device that is reporting error code 0x801901F7.
Go to the Driver tab and press on Uninstall button to uninstall the device driver completely.
Now, install the new driver on your computer.
Restart your computer.
Run virus scan of your PC
Try using a different USB port.
If you do not possess the technical expertise required to accomplish this yourself or do not feel comfortable doing so, download and install a powerful automated tool to get the job done.
If the Task Manager is either blank or is not showing processes on your Windows 10 computer, then here are a few things you can do to resolve this issue. This kind of problem can occur due to some system file corruption or some malware infection in the system.
Here are some suggestions you can try to resolve the problem with the Task Manager on your Windows 10 PC.
Option 1 – Try restarting your computer
The most common and most of the time effective way to resolve this kind of issue is to simply restart your computer. Thus, you have to restart your computer and see if it helps in fixing the Task Manager issue or not. If not, you can try the next given options below.
Option 2 – Run the DISM tool
If the first option didn’t work, then running the Deployment Imaging and Servicing Management tool can help you resolve the issue with the Task Manager as it will repair the Windows System Image as well as the Windows Component Store in Windows 10.
After you access the Advanced Startup options, select Command Prompt by using the arrow keys on your keyboard.
Next, type in this command: DISM /Online /Cleanup-Image /RestoreHealth
Do not close the window if the process takes a while as it will probably take a few minutes to finish.
Option 3 – Make sure that the display columns are selected in the Task Manager
You have to make sure that you have checked or selected the display columns you want to be displayed. So if none of them are selected, you might not see any details at all. Thus, you need to right-click on the space near Name and select the columns.
Option 4 – Run the System File Checker Scan
System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files that might be the reason why the Task Manager is blank or is not showing processes. To run the SFC command, follow the steps given below.
Tap Win + R to launch Run.
Type in cmd in the field and tap Enter.
After opening Command Prompt, type in sfc /scannow
The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:
Windows Resource Protection did not find any integrity violations.
Windows Resource Protection found corrupt files and successfully repaired them.
Windows Resource Protection found corrupt files but was unable to fix some of them.
Restart your computer.
Option 5 – Troubleshot the problem in a Clean Boot State
There are some instances that some conflicting programs installed in your computer might be the one that’s causing the Task Manager issue. To identify which program is causing the problem, you need to put your computer in a Clean Boot State. To do so, follow the steps below.
Log onto your PC as an administrator.
Type in MSConfig in the Start Search to open the System Configuration utility.
From there, go to the General tab and click “Selective startup”.
Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
Next, click the Services tab and select the “Hide All Microsoft Services” check box.
Click Disable all.
Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
From there, start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.
Option 6 – Try scanning your computer using Windows Defender
As mentioned, the Task Manager issue might be caused by some malware in the system and so to eliminate the malware, you have to scan your computer using security programs like Windows Defender.
Tap the Win + I keys to open Update & Security.
Then click on the Windows Security option and open Windows Defender Security Center.
Next, click on Virus & threat protection > Run a new advanced scan.
Now make sure that Full Scan is selected from the menu and then click the Scan Now button to get started.
Virtual Reality or VR for short has come a long way from its infant stage and as 2022 is in half period we are looking at the VR market and reflecting on what has changed in one year. For starters, games have increased in quality and quantity while the hardware price has decreased making the whole VR experience a little closer to a wider audience.
Many companies have tried to get on the VR bandwagon but also many have failed. What remained are staples in VR hardware from large companies that have started with VR early and kept improving their headsets.
So with great pleasure, we are presenting the remaining best 3 virtual headsets so far of 2022 brought to you from Sony, Valve, and Meta.
SONY PLAYSTATION VR
If you want VR on consoles then there is really one option, and that is SONY VR. Premium Virtual Reality solution from SONY, sadly you can do this only on Playstation 4 and Playstation 5. Sony managed to pull off great quality hardware and packed with its exclusives on playstore at a very affordable price that is still cheaper than other products.
While waiting for the Sony PlayStation VR2 headset this one is still a great option and quality is still among the top of the game. From the time of its release until today, many AAA titles have been released for it as exclusives that you can not play any other way and some of them are really worth it.
VALVE Index
Altho there are headsets like HTC Vive Cosmos Elite that have some features that place it as a better solution than Valve Index, Index is still an overall better VR headset as a whole product but its price is something that is keeping it still way out of reach of your standard user. The price, however, is really an illusion since it applies only when buying the system first time, you see Valve has created this headset as a modular design system making it upgradable meaning that you can, for example, buy newer controllers only and they will work perfectly with rest of hardware.
The modular design will save you money when you want to upgrade your VR system but as said entry price is steep. Besides its somewhat higher price than competitors, it is also notable that Index is a positional tracking VR set which means that it relies on a base station in order to locate the user. This means that once set, it is not so easy to change its location of use.
However, its quality and steam use are unmatched, high-quality games and compatibility that no other headset with steam will even pull off probably make Index one of the 3 best headsets out there. Half-life Alyx, arguably and currently one of the best VR games ever made so far was specifically designed for Valve Index and other games are behaving also incredibly nice with this headset, so if you want a great powerhouse for PC VR gaming, you will no go wrong in purchasing Valve Index.
META QUEST 2
Cheapest of the three and coming in various iterations, Meta has established itself from the beginning as a leading player in VR technology with its oculus line of products. Quest 2 is the next product in their line and it comes with 128GB and 256GB versions.
Meta has removed the need for the Facebook account for its VR systems and now you can use them without the need to send any kind of data to meta. Priced fairly for its entry 128 models this standalone VR set improves in any way possible from its previous iteration and sets the bar for what will come in VR's future.
Offering both wired and wi-fi connection with its standalone battery Quest 2 also is packed with a large library of games and it is user friendly as your typical game console but still allows some under-the-hood tinkering if you wish so.
Also, Meta's Vr solution since it uses inside-out tracking makes it incredibly easy to just pick it up and carry it with you wherever you go.
If you are experiencing a Low Wi-Fi signal strength on your Windows 10 PC after you’ve updated or reinstalled it, read on as this post will guide you on what you can do to fix the problem.
The way devices connect these days has evolved with our cognitive revolution. Various devices use some or other wireless technology to connect with other devices. However, all wireless technology has some kind of limitation when it comes to range and signal strength. From time to time, you might have faced several Wi-Fi issues. Low Wi-Fi signal strength usually happens after you update or reinstall your Windows 10 system. This issue can be identified easily by looking at the signal bars in the Wi-Fi icon or by measuring its strength. Since this problem is wide scope, there are tons of possibilities which is why this post covers the most generic situations that could help most users. Refer to the options given below to fix the low Wi-Fi signal strength of your Windows 10 PC.
Option 1 – Try running the Network Adapter Troubleshooter
If a few days ago the range and signal of the Wi-Fi was perfectly fine before you did an update or reinstall, it is possible that there were some changes made in the configuration as well. In most cases, the latest configuration that came with the update has not aligned the config in your computer or laptop. The easiest and simplest way to fix this is by using the Network Adapter Troubleshooter. How? Follow the steps below.
Right-click on the Wi-Fi icon from the system tray to start troubleshooting.
After that, select Troubleshoot problems. Note that it might take a while to run it but once it’s finished, it will show you all the problems with the network adapter.
Note: The Network Adapter Troubleshooter will also fix the issues in the background but there might be some issues that will require manual action. And if the troubleshooter wasn’t able to identify and fix the problem for you, proceed to the next given option below.
Option 2 – Try using the Device Manager
If the problem is related to hardware, you need to seek out the help of the Device Manager. To do so, follow the steps below.
Pull up the Device Manager.
Next, look for your Wi-Fi adapter under the Network Adapters.
Once you found it, right-click on it and open Properties.
After that, you will see all the actions related to drivers under the driver tab.
You can either update or roll back the selected driver or you could also disable and re-enable it to see if the problem’s fixed.
Note: If updating the driver didn’t help, you might have to dig into the advanced settings. From this post on, it can get a bit complicated as there are terms that you might not understand as well as some configuration. To make it easier for you, you can search for your Wi-Fi adapter online and try following the instructions from there. And before you make any further changes to your computer’s settings, make sure that you create a system restore point first.
Option 3 – Try changing the Wi-Fi Roaming Sensitivity
If you want to enhance the Wi-Fi reception as well as the performance on your Windows 10 PC, you might want to change the Wi-Fi Roaming Sensitivity or Aggressiveness. Roaming Sensitivity is the rate at which your computer chooses and switches to the nearest available point of access which offers a better signal. It is based on the strength and quality of the Wi-Fi and not on the distance to the Wi-Fi point.
Option 4 – Try adjusting the Wi-Fi range
The issue could also be caused by the position of your computer with respect to the Wi-Fi router instead of your hardware or drivers. It could be that your physical location might be a factor for the low signal strength of your Wi-Fi so you might want to adjust the Wi-Fi range to fix the problem.
Windows users need to be on high alert. Microsoft has confirmed a critical vulnerability has been found in all versions of Windows which presents an immediate threat, and you need to act now.
A critical new zero-day hack has been found which affects all Windows versions.
Tracked as CVE-2021-34484, the “zero-day” flaw enables hackers to breach all versions of Windows (including Windows 10, Windows 11, and Windows Server 2022) and take control of your computer.
Microsoft mistakenly thought it had patched the vulnerability (which was first found in August) when it was publicly disclosed in October. But the fix itself was found to be flawed, something the company admitted, and this drew even more attention to the vulnerability. Microsoft subsequently promised to “take appropriate action to keep customers protected” but two weeks later, a new fix has still not arrived.
Luckily the third-party security specialist 0patch has beaten Microsoft to the punch with a ‘micropatch that it has now made available for all Windows users “Micropatches for this vulnerability will be free until Microsoft has issued an official fix," 0patch confirmed.
You will need to register for a 0patch account and install its download agent before the fix can be applied, but with 0patch fast becoming a go-to destination for hot fixes which beat software companies to the punch this is a no brainer. Hopes will be high that Microsoft can release an effective patch sooner rather than later but, until then, all Windows users must act now if they want to be safe.
Download 0patch here:
https://blog.0patch.com/2021/11/micropatching-incompletely-patched.html
If you suddenly find the Windows Recovery Environment not working and you see an error message saying, “Could not find the recovery environment”, then you’ve come to the right place as this post will guide you on how you can fix it. In times when you can’t boot into the Windows Recovery Environment, there could be several reasons behind it. However, have you ever wondered where exactly the Windows Recovery Environment is in your computer?
Windows initially places the Windows RE Image file in the installation partition during Windows Setup so if you have installed Windows in the C drive, you can find the Windows RE at the C:/Windows/System32/Recovery or C:/Recovery folder. Keep in mind that this folder is hidden and later on, the system copies the image file into the recovery tools partition to make sure that one can boot into recovery if there are any issues with the drive partition.
The “Could not find the recovery environment” error mostly occurs if the Windows Recovery Environment is disabled or if the “Winre.wim” file is corrupted. Thus, to fix this error, you need to refer to the given suggestions below.
Option 1 – Try to enable Windows Recovery Environment
In the Windows Start Search, type “PowerShell” and from the search results that appear, right-click on Windows PowerShell and then select the “Run as administrator” option to open it with admin privileges.
Next, type the “reagentc /info” command and tap Enter to execute it.
After that, if the output states that Status is enabled, then you’re all set.
Now type the “reagentc /enable” command and tap Enter to enable the Windows Recovery Environment. You will see a success message at the end signifying that Windows RE is available.
Option 2 – Try to fix the corrupted or missing “Winre.wim” file
If the Winre.wim file is either corrupted or missing, you need to get a new copy of this file from another computer where the Windows RE is working. Once you’re able to get a new copy of the Winre.wim file, you have to set the image path to a new location. For more details, refer to these steps:
First, type “Powershell” in Windows Start Search and right-click on Windows PowerShell from the results, and select Run as administrator.
Next, execute the given command below to change the path of the WIM file to the new location. Note that the steps should be used when the file path of the Windows Recovery Environment is different from the usual spot.
Reagentc /setreimage /path C:RecoveryWindowsRE
As mentioned, if the file is corrupted, you just have to get a new copy from another PC but before you do that, make sure that the WINRE on that computer is disabled (just enable it later on) and then place it in the C:/Recovery path and then set its path again using the command given above and then verify its path by executing the following command.
reagentc /info command
Note: Since the Recovery folder is hidden as well as the WINRE folder in it and you won’t be able to access them using the Windows File Explorer, you need to use the Windows PowerShell or Command Prompt so that you can access them.
Option 3 – Try checking and fixing the WinRE Reference in the Windows Boot Loader
The Windows Boot Loader is the one that determines if it has to load the Windows Recovery Environment. It could be that the boot loader is pointing to an incorrect location which is why you’re getting the error. To resolve it, you have to check and fix the WinRE Reference in the boot loader. How? Follow these steps:
In the Windows Start Search, type “PowerShell” and from the search results that appear, right-click on Windows PowerShell and then select the “Run as administrator” option to open it with admin privileges.
After that, execute the “bcdedit /enum all” command.
Next, look for an entry in the Windows Boot Loader identifier set as Current and look for “recoverysequence” in that section and take note of the GUID.
Ensure that the device and the osdevice items show the path for the Winre.wim file and that they are the same. If not, you need to point the current identifier to the one which has the same.
Once you’ve found the new GUID, execute this command: bcdedit /set {current} recoverysequence {GUID_which_has_same_path_of_device_and_device}
Now check if the error in the Recovery Environment is fixed or not.
Option 4 – Try creating a Recovery Media
You could also try creating a Recovery Media to resolve the error in the Windows RE. All you have to do is download the Windows 10 ISO file using the Media Creation tool and then create a recovery drive. Once you’re done, check if it fixes the problem or not.
Task View feature inside Windows 11 is actually a great feature, letting you quickly view open windows and virtual desktops. How Task view itself could be reached with keyboard shortcut combination of ⊞ WINDOWS + TAB some users will prefer this way of using it and thus button on the taskbar is something you do not want or need.
Bypass TPM with changing installation media
Tracked as CVE-2021-34484, the “zero-day” flaw enables hackers to breach all versions of Windows (including Windows 10, Windows 11, and Windows Server 2022) and take control of your computer.
Microsoft mistakenly thought it had patched the vulnerability (which was first found in August) when it was publicly disclosed in October. But the fix itself was found to be flawed, something the company admitted, and this drew even more attention to the vulnerability. Microsoft subsequently promised to “take appropriate action to keep customers protected” but two weeks later, a new fix has still not arrived.
Luckily the third-party security specialist 0patch has beaten Microsoft to the punch with a ‘micropatch that it has now made available for all Windows users “Micropatches for this vulnerability will be free until Microsoft has issued an official fix," 0patch confirmed.
You will need to register for a 0patch account and install its download agent before the fix can be applied, but with 0patch fast becoming a go-to destination for hot fixes which beat software companies to the punch this is a no brainer. Hopes will be high that Microsoft can release an effective patch sooner rather than later but, until then, all Windows users must act now if they want to be safe.
Download 0patch here:
