The New and upcoming HAF 700 Evo from Coller master is a beast of a case, but so is its price. The case itself is still not released but as sources say it will be soon, well at least we hope so. The price will be around $500 which is a little on the expensive side of things but the features it is bringing are very impressive.
HAF 700 EVO Size and its advantages
HAF stands for High Airflow and with this case, you are going to get it but first let us talk about other characteristics of the case. Firstly case is ATX full tower, pretty big going 24.64 x 11.45. x 26.22 inches in size but like all full tower cases it can hold all motherboard types including Mini-ITX, Micro-ATX, ATX, E-ATX. The large case size also lets you place a pretty big GPU, going to 19.29 inches (490 mm) in its length covering currently all available Graphic cards on market.
Being a very big computer case is not just placing motherboard and big GPU, there are other great advantages of it, firstly that you can go wild with your CPU cooler, going all the way to 6.5 inches in cooler height will satisfy all users and having 12x 2.5 or 3.5-inch internal bays will. And if even that is not enough you have 8 expansion slots available.
Inside HAF 700 EVO
Inside the casing you will also find 2 front fans with 200mm diameter, 2 rear fans sized 120mm, and 1 bottom fan of 120mm. You can also manually mount standard 120mm fans on top of the case for maximum airflow.
Front panel and outsides
The front side is filled with 4x USB 3.2 Gen 1 Type-A (5 Gbps), 1X USB Type-C (up to 10Gbps), 3.5mm both headphone and audio jack along with a reset switch. Also, the circle in the very front is a hi-resolution LCD customizable display, you know, just to add more flavor and personal touch to the case. Fron is also filled with glass panels emitting RGB light.
Of course, you must also have a Tempered Glass Side Panel and well weight of 53.57 pounds (24.3 kg), yup you read that correctly, beside its hefty price tag this cooler master beast also is pretty heavy. Granted all of the weight comes from the glass front panel it is still a little hard on moving and taking out of the box.
This is also the case where you will not need a single screwdriver, everything is made to be assembled with your hands alone pushing easy assembly into the front row.
Conclusion
So in the end what are my thoughts about this expensive and heavy PC case? Would I recommend it? The answer to that question could depend really on your budget, let us be really honest here if you can afford it, YES, wholeheartedly I would recommend the case, it is great, it feels great, it looks great and the airflow is amazing. However, if you are tight on a budget, there are other great cases with excellent airflow and you might want to skip this one.
nVIDIA is one of the behemoths of the GPU world, but that not means that they are perfect and that they do not make mistakes, throw WIndows in the mix, and sometimes you have issues with your nVIDIA display drivers for various reasons which could get very unpleasant. But do not worry, we have your back and in this article, we will focus and help you to resolve common nVIDIA driver issues. So sit back and let's start with the repairs.
Rollback to the previous driver and stop automatic updates.
nVIDIA sometimes publishes really messy drivers which can really cause some serious issues, if by any chance you managed to be unlucky enough to get this kind of driver, do not despair, roll back to the previous working version and wait for the fix.
To stop Windows from doing automatic driver updates, navigate to Control Panel > System & Security > System > Advanced System Settings > Hardware > Device Installation Settings. Then choose "No (your device might not work as expected)".
Once you have turned off automatic driver updates, uninstall your current driver and install the previous version from the official nVIDIA website.
Reboot your system
Reinstall nVIDIA driver
Reinstalling the driver might fix the issue if by any chance driver files got corrupted during download for example.
First, you will need to delete some files in order to perform a clean installation.
Log in as administrator if you are not one and delete following files and folders:
C:\Windows\System32\DriverStore\FileRepository\nvdsp.inf fileC:\Windows\System32\DriverStore\FileRepository\nv_lh fileC:\Windows\System32\DriverStore\FileRepository\nvoclock fileC:\Program Files\NVIDIA Corporation\C:\Program Files (x86)\NVIDIA Corporation\Reboot your system
Start driver installation again, choose custom installation, then clean install.
Update driver in the Device Manager
If driver updates for any reason can not work via the official install package from nVDIDA, try updating the driver in the Device Manager
Navigate to Device Manager, expand graphic adapters, right-click on your nVIDIA device and click on update driver.
Reboot your system
That's it, 3 solutions on how to remove, reinstall and update your nVIDIA driver, thank you for reading and I hope to see you again.
If you are testing your headphone or your speaker but all of a sudden encountered an error that says, “Failed to play test tone” in your Windows 10 computer, worry not for this post will walk you through how you can fix this problem.
The test tone is used to check the right-left balance of the headphones and speakers in your computer, however, if you are not able to use it, there are several options you can check out. You can try to run the Playing Audio troubleshooter or restart the services that are related to Windows Audio. Aside from these, you could also disable Audio Enhancements or you could also change the default test tone rate and bit depth.
Option 1 – Try to run the Playing Audio Troubleshooter
Since the Windows 10 operating system has the Playing Audio Troubleshooter, you can use this troubleshooter to try and fix the problem with the “No Audio Output Device is installed” error. You can access this tool in the Control Panel or in the Taskbar Search and even on the Troubleshooters page of Windows 10.
Run this troubleshooter and see if it can fix the issue or not.
Option 2 – Try to restart the Windows Audio-related services
The next thing you can do to fix the problem is to restart the services related to Windows Audio. Although the audio services start automatically on every system boot, there are times when they might fail to start. Thus, you can start these services manually by following these steps:
Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and hit Enter to open the Services Manager.
Then look for the services named “Windows Audio” and “Windows Audio Endpoint Builder”.
Double click on each one of these services and check if their Service Status is set to Running or not and also check if the Startup Type is set to Automatic.
If none of the services are running, just click on the Start button and select the Automatic option from the drop-down menu.
Now click on the Apply and OK buttons to save the changes made and then check if the error is fixed.
Option 3 – Try to update the Audio driver
You might also want to consider updating or the Audio driver as it could help in fixing the error.
Tap the Win + R keys to open the Run dialog box and then type in devmgmt.msc and tap Enter or click OK to open the Device Manager.
Expand the section for the outdated device drivers.
And then select the outdated driver(s) and right-click on it/them.
From the drop-down menu, select the Update Driver option and follow the on-screen instructions to install the latest version of the driver.
Then also click on the option, “Search automatically for updated driver software.
Restart your PC after the installation.
Note: If updating or reinstalling the Audio driver didn’t work, you can go to the manufacturer’s website and look for the support section where you can download the drivers for your computer. You just need to take note of your PC’s correct model and model number so you can find the appropriate driver.
Option 4 – Try changing the default test tone rate and bit depth
Windows selects a default test tone rate and bit depth depending on your headphone or speaker. This allows you to look for the best sound quality from your audio output device. So if your headphone or speaker has some problems with the default settings, then it’s no wonder why you’re getting the “Failed to play test tone” error. To fix this, you can try to change the default test tone rate and bit depth by following the steps below.
First, you need to open the Windows Settings panel and then go to System > Sound.
Next, look for the Device properties option located on your right-hand side and click on it.
After that, select the Additional device properties option and go to the Advanced tab.
From there, select a different test tone rate and bit depth and then click on the Test button.
Once done, check if it was able to fix the problem or not.
Option 5 – Try disabling the Sound or Audio enhancements
To make your operating system’s specific hardware sound nothing but perfect, both Microsoft and third-party vendors have shipped audio enhancement packages which are usually referred to as “Audio Enhancements” in Windows 10. However, there are instances when instead of improving the sound or audio quality of your computer, it can cause problems so to fix the problem you need to turn off these audio enhancements. How? Simply follow the steps below.
Type in “Sound” in the taskbar search and then from the list of results, select “Sound Control Panel”.
After clicking Sound, the Sound properties box will pop up. From there, go to the Playback tab and right-click on the default device i.e. Speakers or Headphones then select Properties.
After that, the Speakers properties box will appear. From there, go to the Enhancements tab and select the checkbox for the “Disable all enhancements” option.
Error Code 49 is a common device driver error that users encounter on any Windows 2000 and later operating system versions.
The error occurs when the connected peripheral devices fail to function properly due to an overload of the system hive’s size.
The error when prompted pops up on your screen with the following message:
"Windows cannot start new hardware devices because the system hive is too large (exceeds the Registry Size Limit). (Code 49)”
The error causes unattached devices to be displayed on the system hive list.
Solution
Error Causes
Error Code 49 mainly results from problems in Windows registry system files; the system hive in the Windows registry exceeds its size limit.
The system hive is part of the Windows registry and it is where files regarding devices are contained along with user preferences and applications.
The devices will not work until the system hive size is brought back to normal levels.
Further Information and Manual Repair
There are several ways you can use to fix your error code. Here are the following.
Method 1 – Uninstall unused devices
One of the best ways to address the error code is to uninstall the unused devices which are listed on your computer’s system hive. To do this:
Log in using an Administrator account
Click the Start button and then click ‘Run’
In the box, enter the command:
"set devmgr_show_nonpresent_devices=1 cd%SystemRoot%System32 exit"and click enter
Open Device Manager, click ‘View’, and then choose ‘Show hidden devices’ to see unused devices.
When you can see the list, click on the device you want to uninstall by selecting the ‘Driver’ tab and then select ‘Uninstall’.
After uninstall is complete, restart your computer.
Method 2 – Use System Restore
If the error still persists, you can use system restore to eliminate the problem. Here is how you can do so:
Log in using an Administrator account
Click ‘Start’ button and select All Programs > Accessories > System Tools > System Restore
Click ‘Restore my computer to an earlier time’ and click ‘Next’
Select the last Windows restore point from the ‘On this list, click a restore point’ list, and click ‘Next’
Click ‘Next’ on the confirmation window to proceed
Restart your PC after restoration is complete
By restoring the system via a last saved system checkpoint, you can obtain undamaged Windows system files that can help avert the error code.
Method 3 – Manually uninstall and reinstall the device driver
If using system restore does not work in resolving the error code either, you may have to resort to manually uninstalling and then reinstalling the device driver causing the problem.
This would be necessary since the remaining incomplete files due to a partial removal or installation of programs is what results in the error code. By uninstall and reinstalling the device driver program, it would lead to the completion of the files.
You can do this by firstly logging in as Administrator and open Device Manager. Select the device that is causing the problem and double click it and make sure that the peripheral is connected properly to the PC.
Upon opening, click on the ‘Driver’ tab and then select ‘Update Driver’. Make sure to refer to the system documentation that you received with your PC or computer to check for the motherboard details and driver specifics.
Method 4 – Use software to automatically download the driver
Manually uninstalling and reinstalling the driver will do the trick; however, it may be time-consuming, especially when you would have to resort to your hardware user manual.
Therefore, using a program such as DriverFIX can save you a lot of time and frustration in having your device work properly on your computer.
DriverFIX, with its user-friendly approach to help you fix your PC issues, comes with an integrated database that detects which drivers you need to reconfigure within just a few seconds and downloads it automatically.
It further ensures that your drivers are installed in their entirety leaving no room for any incomplete files to remain that create Error Code 49.
It also has the added advantage of being able to backup and restore your files should there be the slightest possibility of system file damage. DriverFIX is the answer to fixing your PC error codes accurately and quickly.
Click here to download DriverFIX to fix Error Code 49 quickly and effectively!
If you encounter Windows Update error 0x80092004 while trying to update your Windows 10 computer, then this post is for you. This kind of Windows Update error could be due to many reasons but none of them includes your hardware or installed driver software. Microsoft releases updates that are either not supposed to go out, or you install them when you click on the Check for Update button which can install updates that have not finished testing yet. As a result, you may encounter the Windows Update error 0x80092004
To resolve the Windows Update error 0x80092004, here are some fixes you can try.
Option 1 – Try removing recent updates and packages
When a Windows Update fails, it mostly rolls back and cleans up all its residues. However, there are times when it doesn’t and you can clean that package manually. To remove recent updates and packages, you can go to the Update History and find out what KB updates were installed and once you’ve figured it out, you can execute the DISM tool to remove it manually.
Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
After that, execute the “Dism /online /Get-Packages”. This will give you a list of packages that were recently installed.
Now run the Remove Package program to remove the concerned update and package.
Note: Keep in mind that the remove package command is made for AMD 64-bit machines specifically.
Option 2 – Try deleting the files from the SoftwareDistribution folder and resetting the Catroot2 folder
The downloaded Windows Updates are placed in a folder called “SoftwareDistribution”. The files downloaded in this folder are automatically deleted once the installation is completed. However, if the files are not clean up or if the installation is still pending, you can delete all the files in this folder after you pause the Windows Update service. For complete instructions, refer to the steps below.
Open the WinX Menu.
From there, open Command Prompt as admin.
Then type in the following command – don’t forget to hit Enter right after typing each one of them.
net stop wuauservnet start cryptSvcnet start bitsnet start msiserver
After entering these commands, it will stop the Windows Update Service, Background Intelligent Transfer Service (BITS), Cryptographic, and the MSI Installer
Next, go to the C:/Windows/SoftwareDistribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.
After resetting the SoftwareDistribution folder, you need to reset the Catroot2 folder to restart the services you just stopped. To do that, follow these steps:
Type each one of the following commands.
net start wuauservnet start cryptSvcnet start bitsnet start msiserver
After that, exit Command Prompt and restart your computer.
Option 3 – Try to run the Windows Update Troubleshooter
Running the built-in Windows Update troubleshooter could also help you resolve the “We couldn’t install some updates because the PC was turned off” error. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.
Option 4 – Try to manually install the Windows Updates
Windows Update Error 0x80092004 might be due to a Windows Update that has failed. So if it is not a feature update and only a cumulative update, you can download the Windows Update and install it manually. But first, you need to find out which update has failed, and to do so, refer to the following steps:
Go to Settings and from there go to Update and Security > View Update History.
Next, check which particular update has failed. Note that Updates that have failed to install will be displayed under the Status column which has a label of “Failed”.
After that, go to the Microsoft Download Center and look for that update using its KB number and once you find it, download and then install it manually.
Note: You can also use the Microsoft Update Catalog, a service from Microsoft that provides a list of software updates that can be distributed over a corporate network. With the help of this service, it can be easier for you to find Microsoft software updates, drivers as well as fixes.
If you suddenly encounter an error message that says, “This webpage is not available, Err_Connection_Closed” while browsing the internet or visiting a website and the website fails to load, then it means that there is some problem with your network connection. Similarly, you may also get other error messages like “Err_Network_Changed”, “Err_Connection_Reset” and “Err_Internet_Disconnected” errors in different browsers like Chrome, Firefox, and Edge.
The problem lies in your Windows 10 computer and your internet connection since this is a network issue. So before you troubleshoot the problem using the suggestions given below, you need to refresh your browser first or you could also tap Ctrl + F5 on your keyboard to hard reload the webpage. If you’re still getting the same error message, then proceed to the guide below.
Option 1 – Try removing the Proxy
Removing the Proxy might also help you in fixing the “This webpage is not available, Err_Connection_Closed” error. Here’s how you can do it:
Tap the Win + R keys to open the Run dialog box.
Then type “inetcpl.cpl” in the field and hit Enter to pull up the Internet Properties.
After that, go to the Connections tab and select the LAN settings.
From there. Uncheck the “Use a Proxy Server” option for your LAN and then make sure that the “Automatically detect settings” option is checked.
Now click the OK and the Apply buttons.
Restart your PC.
Note: If you are using a third-party proxy service, you have to disable it.
Option 2 – Try using Google Public DNS
If the first option didn’t resolve the issue, you can try to use the Public DNS by Google and see if it can help fix the problem. You have to modify the DNS settings in your system explicitly and use the DNS IP addresses.
The first thing you have to do is right-click on the network icon in the Taskbar and select Network and Sharing Center.
Next, click on the “Change Adapter Settings” option.
After that, search for the network connection that you are using to connect to the internet. Note that the option might be “Wireless Connection” or “Local Area Connection”.
Right-click on your network connection and click on Properties.
Then select the new window to choose the “Internet Protocol 4 (TCP/IPv4)” option.
After that, click on the Properties button and click the checkbox in the new window for the option “Use the following DNS server addresses”.
Type in “8.8.8.8” and “8.8.4.4” and click OK and exit.
Option 3 – Reset Winsock, TCP/IP & Flush DNS
Resetting Winsock, TCP/IP, and flushing DNS might help you resolve the Err_Connection_Closed error. To do so, follow these steps:
Right-click on the Start button and click on Command Prompt (administrator) so you can pull up an elevated Command Prompt.
After that, execute each one of the commands listed below. And after you typed in one after the other, you have to hit Enter.
netsh winsock reset – type in this command to reset Winsock
netsh int ip reset resettcpip.txt – type in this command to reset TCP/IP
ipconfig /flushdns – type in this command to flush the DNS cache
Next, restart your PC and check if the problem’s fixed.
Option 4 – Disable both the Antivirus program and Firewall temporarily
There are times when antivirus programs and the firewall blocks a website that they consider to be malicious or even because of false-positive effects which is why you have to disable these programs temporarily as it might be the reason why you’re getting the “This webpage is not available, Err_Connection_Closed” error when trying to browse the internet.
Option 5 – Try to check the network cables and then restart your router
The most obvious thing you can do first is to try checking if the network cables connected to your computer or router are properly connected or not. If it turns out that some network cables are not connected properly, then it’s probably why you’re getting this error.
Option 6 –Try a Network Reset
When all else fails, you might have to consider resetting your entire network settings. Simply follow the steps below to do so.
Click on the Start button and then click on the gear-like icon for Settings to open it.
Next, select Network and Internet.
Then scroll down and look for “Network Reset” – click on it and then click on the Reset now button.
In case you don’t know, Windows contains a feedback mechanism that generates error reports from hardware and software problems. These reports are temporarily stored in the system and send them back to Microsoft so that it can find solutions to the reported problems and fix them in the upcoming updates. However, as time goes by, these reports actually take a lot of space in your computer which is why end-users like you are free to delete them with the help of the new Free Up Space feature in Windows 10.
As useful the Free Up Space feature may be, there are times when you won’t be able to use it for some reason which is why in this post, you will be guided on how to use alternative ways in deleting very large System queued Windows Error Reporting file, some of which may run in Gigabytes.
Every time the Windows Error Reporting or WER sends out an error file and looks for a solution, the WER server at Microsoft sends out a solution instantly. And if the solution is under investigation or is unknown, then you will be notified about it right away and will be asked for more details.
As mentioned, even though the Free Up Space feature in Settings will be able to clear the error reporting files, there are instances when it won’t be able to delete very large System queued Windows Error Reporting files. Alternatively, there is an option to delete these files using the Disk Cleanup Utility.
Feel free to select which option you’d like to use to get rid of Windows Error Reporting Files.
Option 1 – Delete Windows Error Reporting Files via Settings
Go to Settings.
From there, go to System > Storage > Free Up Space and then click on it to launch it.
Afterward, give it some time to populate all the files and folders. Once it’s done, select “System created Windows Error Reporting files” to mark its checkbox while leaving the other options unchecked.
Next, click on the Remove files button to delete all the Windows Error Reporting files from your computer.
Option 2 – Manually delete the Windows Error Reporting Files
Tap the Win + E keys to open File Explorer.
Next, enable the Hidden Files view from the menu.
Then go to C:/ProgramData/MicrosoftWindowsWER.
From there, you will see various folders like LocalReportArchive, ReportArchive, ReportQueue, and Temp.
Open each one of the aforementioned folders and delete the archive files. Note that these files will have names similar to “00c58c1f-b836-4703-9bcf-c699ca24d285”.
Note: If you are not able to delete any of these files, you have to take ownership of the folder. To do so, refer to these steps:
Right-click on the folder and then select Properties.
Next, click on the Edit button in the Properties window and click OK to confirm if you got a User Account Control elevation request.
After that, select user/group from the permission windows or click on the Add button to add another user or group. It would be best if you add “Everyone” to give permission.
Then check “Full Control” under the “Allow” column to assign full access rights control permissions.
Now edit the permission to Full Control for “Everyone”.
Click OK to save the changes made and then exit.
On the other hand, if you do not want to go through all these troubles in deleting the Windows Error Reporting files, you can just disable it especially if it already becomes a daily annoyance as the files generate every day and their sizes are mostly gigabytes. And besides, there are times when these files do not make it to the Microsoft WER server and end up only occupying a lot of space for nothing.
When Windows is installed on a clean hard drive it usually finds most of the needed drivers for our computer to run, but if we by any chance have any old unsupported hardware or some exotic one chance are very high that Windows will not be able to locate and install drivers for it.
And sometimes we do not even have drivers from where to download them, let's say for example you have purchased a second-hand laptop with Windows on it, you wish to create a clean and fresh copy of new Windows installation but you do not have drivers, and let us say the model is not supported so you can not download them. In this case, this shown method will help you a ton and save you a lot of time and frustration.
So, in order to back all of your drivers from your Windows follow this simple guide step by step. Note please that this method will backup drivers themselves, you will not backup installation packages of drivers or similar stuff, only drivers installed in Windows itself.
Backing up the drivers
First thing first, create a folder where you want your drivers to be backed up somewhere in your HD and give it any name.
Second, press ⊞ WINDOWS + X to open the secret Windows menu.
From the menu choose Command Prompt (administrator)
When the command prompt is active type the next command in it:
DISM /online /export-driver /destination:C:\DriverBackup
where: C:\DriverBackup is the folder and the hard drive where you want to store your backed-up drivers.
Press ENTER
That's it, you have now successfully backed-up all of your installed Windows drivers.
Now, save all of your drivers on USB and reinstall Windows.
In order to now return backed drivers do the following:
Press again ⊞ WINDOWS + X to open the secret Windows menu.
but this time choose Device manager
From decide, manager right-click on any device Windows has not been able to install appropriate driver and choose update driver
Click on the Browse my computer for driver software option.
Error 1713 is essentially a programming error. It has specifically been designed in Microsoft applications. This is intended to allow customers to continue using the appropriate setup tool.
The error can be quite annoying and is used by manufacturers to determine what caused the error so that counteractive methods can be employed. The number 1713 is simply the hexadecimal code that informs where the instruction was loaded when the error occurred.
Solution
Error Causes
As far as the causes of Error 1713 are in question, the primary cause is damaged, misconfigured, or corrupt windows system files. There are several other factors that lead to the occurrence of Error 1713.
For instance, if the applications or hardware on your system has been improperly deleted, installed, or uninstalled, Error 1713 will occur.
Similarly, Error 1713 is triggered when the computer has recovered from an attack by some virus, spyware, malware, or adware only recently. This attack corrupts the file and so the error appears. Incorrect system shutdown can also be blamed for this error.
All the scenarios listed above actually damages the registry entries in Windows system files.
The corrupt or damaged files will then lead to improperly linked or missing information. It goes without saying that such problems will keep the applications from performing in the desired manner and this makes it even more crucial to fix this error as soon as it appears.
Further Information and Manual Repair
Two of the most useful workarounds for Error 1713 are listed below.
This solution is for advanced users. Restart your computer. Log on to it as the admin in the safe mode. Now go to the Start button and follow this path All Programs-> Accessories-> System Tools->System Restore. Now an option will appear asking you to ‘Restore your computer to an earlier time’. Select it. This option will actually appear in a new window. Click Next. A list of restore points will be displayed to you. Select the most recent restore point before the occurrence of the error and press Next. Now click on the Next button that appears in the confirmation window. Restart your computer as soon as the restoration is finished.
This solution is for novice users. Download a 1713 repair utility available online. Install this program and use it to scan your system. After the scan is complete, click on repair to fix the error.
Some users wanting to upgrade to Windows 10 from Windows 7 or Windows 8.1 experienced errors with installation. One of these errors is CPU Not Compatible. When you click and run the “Get Windows 10” from your system tray bar, you’ll receive the “CPU is not compatible with Windows 10” error. When this happens, it might be good to check if there’s a bug or if your NX feature (a requirement for the Windows 10 installation) is enabled.
Solution
Error Causes
The “CPU is not compatible with Windows 10” error normally occurs when:
NX feature is not enabled
You experienced the Windows 10 bug
Further Information and Manual Repair
To successfully upgrade to Windows 10, your CPU must support Physical Address Extension (PAE), SSE2, and NX features. If any of these features are not activated on your system, it’ll cause the CPU not compatible error. However, some users still reported experiencing this error even though their CPU has these features activated. Normally, this is due to the bug that Windows acknowledged.
If any of these two scenarios apply to your computer, the following methods will help you fix the problem:
Method 1 – Check for bugs
The bug applies to some Windows 7 and Windows 8.1 systems. The bug occurs when the “Get Windows 10” app fails to recognize CPUs as being compatible. This produces a false negative result with a message, “Here’s why Windows 10 cannot be installed on this PC: The CPU isn’t supported”. To fix this bug, Microsoft released an update.
Unfortunately, the patch update (KB2976978 for Windows 8/8.1 and KB2952664 for Windows 7 SP1) to fix the bug may not be automatically downloaded to your computer. If this is the case, you need to verify first if the patch was installed correctly. To do this, follow the steps below:
Click ‘Start’ and type in View Installed Updates. The “View installed updates” icon should appear. Click the icon.
Go to the Search bar (Top right portion) then type the patch name for your system. Make sure that you type the correct patch name for your system since Windows 7 and Windows 8/8.1 have different names. If you find the patch, it means it’s already installed. You can now upgrade to Windows 10 without the CPU not-compatible error.
But, if you can’t find it you need to install the patch manually.
Go to Windows Update then click the “Check for Updates” button.
Browse through the available updates and look for KB2976978 for Windows 8/8.1 or KB2952664 for Windows 7 SP1
Download the right patch. You may need to reboot your system once it’s done.
The downloaded patch should be applied after a day or two with the Windows Task Scheduler. Once the patch is applied, you can now upgrade to Windows 10.
Method 2 – Check CPU features and activate them if needed
A major requirement for Windows 10 upgrade is for the CPU to have Physical Address Extension (PAE), SSE2, and NX features enabled on your system. If you receive the CPU not compatible error, one possible cause is that any of the mentioned features are not available OR not enabled on your system. Here’s how you can fix this:
Verify if your CPU supports the three instruction sets. You can use software that provides information like this. If all three are available, proceed to the next step.
Go to your computer’s BIOS. To do this, reboot your computer. You will need to press a key specific to your computer’s manufacturer (usually it’s F12, F8, F2, or DEL).
Look for the NX (No Execute Bit) settings. This is normally found in the “Advanced Configuration” menu, or something similar to this. Just take note that the NX setting can be named differently in BIOS. Some other names include EDB (Execute Disabled Bit), EVP (Enhanced Virus Protection), Execute Disabled Memory Protection or No Excuse Memory Protect.
Once you’re in the NX settings, make sure that it’s enabled.
Exit the BIOS and SAVE your changes.
Boot your computer normally, then try upgrading to Windows 10 again through the “Get Windows 10” app found in the system tray.
Method 3 – Force enabling NX Bit
If changing the settings in your BIOS doesn’t do the trick, your final option is to force enable the NX bit in your Windows system. However, this is only applicable IF and ONLY IF your CPU does support it. To force enable NX bit, do the following:
Click Start and go to command prompt (Type “cmd” – no quotes) and press enter.
Copy and paste the text below to the command prompt.bcdedit.exe /set {current} nx AlwaysOn
Execute the command. You will need to reboot your computer once this is done.
Download and install Windows 10
Method 4 – Use a trusted automated tool
If you still experience the error after doing the methods above, you might want to try a powerful and trusted automated tool to fix the job.
We have talked about gaming on old computers and have covered new and upcoming Steam deck handheld console. Today we are combining old gaming with a handheld console and our target of talk is Retroid pocket 2. This product is packed with really high-quality plastic and with some great features in it.
So let's dive into this cool handheld in more detail and find out why we like it so much.
Good manufacturing quality
Plastic and overall manufacturing quality are really, really good. The battery is great, packing 4000mAh that can hold over 3 hours of nonstop gaming, and all buttons and joysticks are great. The screen is a 640 x 480 60Hz 3.5″ IPS screen (4:3 aspect ratio) that performs really great for its purpose, retro gaming. There is a Digital D-Pad and dual analog joysticks. The right joystick is the lower profile to avoid being accidentally moved when pressing the four gaming buttons. There are three buttons at the bottom which are Home, Start, and Select. On either side are good-quality stereo speakers. On the bottom of the device are a Micro SD Card slot and a 3.5mm headphone port. On the top of the device are Left and Right shoulder and trigger buttons. There are the power button and volume adjustments. There are a USB Type-C OTG port and a Micro HDMI output for connection to a TV.
Good technical statistics
Good, not great but then again since this is retro handheld you cannot really expect some crazy stuff like alder lake inside. So the console is punching ARM Cortex A7 CPU with 2 cores and a clock of 1.5GHz paired with ARM Mali 400-MP2 500MHz GPU. The console has 1GB LPDDR3 RAM memory and 8GB eMMC Storage where 5GB is freely available, the rest is taken for OS. As mentioned before the display is 640x480 resolution with a size of 3.5″. The battery is Lithium-Ion with a power of 4000mAh and on the handheld, there is a USB Type-C connector, 3.5mm headphone jack, and Micro-HDMI. It also has Wifi/Bluetooth 4.0
Retroid Pocket 2 OS and support
Pocket 2 comes with Android 6 but you can update its firmware to the 8.1 version on the official site that I would highly recommend. New versions of the handheld will come with 8.1 on it from the box. Having Android as OS opens many possibilities like you can download Android apps such as Steam Link, allowing you to play actual PC games on your Retroid Pocket 2. Not just that, if it does get a newer version of Android it could even have the ability to use xCloud, Xbox’s cloud gaming service. Of course, hardware will not be able to handle modern games but the option is still there and for some old PC titles available on steam like Commander Keen, for example, this is a great option.
The console can emulate basically everything up to Dreamcast, including N64, PSP, and Playstation 1. It can emulate Nintendo DS also, but it can only do so with one screen. The only problem with this console is you will need to install and update Apps. You’ll need to learn about RetroArch, an app that lets you download emulators or cores to play games.
Retroid price
The last thing on the list is the price of the console itself. Going just under the 100$ mark this really makes it an affordable option for plenty of people that would like to experience retro handheld gaming or for ones like me, nostalgic gamers wanting to relive some era of playing games on the road.
Conclusion
Among Chinese handheld devices for retro gaming, Retroid Pocket 2 is really on top of what the market can offer. If you are looking for a great handheld retro console and are not afraid of little dive-ins into the OS and various configurations, Pocket 2 will reward you with plenty and wide emulation support.