MS releases ISO for Windows 10 build 21354

Can not open and run EXE file in Windows is not a new issue and sadly it can still happen from time to time, luckily this step by step solution will help you to resolve this problem fast and effective in no time. Try the below solutions in no particular order and I hope that you will solve the issue fast and be able to return to using the computer like it never happened

1. Run SFC scan

   As the EXE file not opening issue lies in the Windows OS, the SFC tool will be able to identify the cause and fix this issue. Press ⊞ WINDOWS + X and choose command prompt (admin) in command prompt type: sfc /scannow Press ENTER

2. Check registry and modify if needed

   Sometimes value in the registry key is wrong and can cause this error, in order to check if this is the case, we will open the registry editor and find out Press ⊞ WINDOWS + R to bring run dialog up type in it: RegEdit and press ENTER In the left pane of the Registry Editor window, click on the HKEY_CLASSES_ROOT to expand the section Scroll down to find out the .exe registry and click on it Go to the right pane of the window and double-click on the Default and set the Value Data as exefile Click on the OK button Next, located the given in the window: HKEY_CLASSES_ROOT>exefile>shell>open>command Click on the “Command” in the left pane of the window In the right pane of the window double-click on the Default and set Value Data as “%1” %* Click on the OK button Restart your computer and check if the issue persists

3. Turn off Firewall and defender

   If you have a firewall and antivirus active there might be a chance of a conflict and that firewall or antivirus is preventing the EXE file from starting, disable your firewall and anti-virus and try again to open the EXE file.

4. Turn off user account control

   User account control can also like a firewall prevent some files from executing, go into accounts and turn off user account control to see if this might be an issue preventing you from opening the file.

Experiencing issues while using Remote Desktop connections is not uncommon. One of the issues that users encountered recently while trying to connect to their Remote Desktop network is the error saying, “Your credentials did not work, The login attempt failed”. If you are one of these users, then you’ve come to the right place as this post will walk you through fixing the problem. When facing this kind of problem, the first thing you can try before you do some troubleshooting steps is to verify the credentials. But if you are certain that you’ve entered the correct credentials just like what other users reported, then it’s completely a different matter. Based on the reports, this error is common on newly installed versions of Windows 10 or after reinstalling the operating system which could mean that the problem might be due to the Windows security policies or the username might have been recently modified. The latter case is a possibility especially if you’ve reinstalled Windows 10 and had entered a new username. In such a case, you will really have a difficult time connecting to your Remote Desktop connection since its credentials do not really automatically change. If you’ve verified that your credentials are correct, then now’s the time you troubleshoot the problem with the help of the potential fixes provided below. Just make sure that you follow each one of them in sequence.

Option 1 –Try to run the Network Adapter troubleshooter

To run the Network Troubleshooter, refer to these steps:

• Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
• Next, scroll down and select the “Network Adapter” option from the right pane.
• Then click on the Run Troubleshooter” button.
• After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.
• Restart your computer.

Option 2 – Try to change the network profile from public to private

According to some reports, this error occurs on systems where the network profile was set to public. Thus, you need to change the network profile to private to resolve the problem. How? Refer to these steps:

• Go to Start and from there click on Settings > Network & Internet > Status.
• Next, click on the “Change connection properties” option.
• After that, set the radio button of Network Profile from Public to Private.
• Wait for a couple of seconds until the system is done applying the changes you’ve made and then see if you can now connect to the Remote Desktop connection.

Option 3 – Try changing the account username

As mentioned, one of the possible causes for this error is the reinstallation of the operating system. You might have changed the username for the system but it does not really change the username of the Remote Desktop connection as well. Thus, you have to change the username back to what it was before you’ve reinstalled Windows 10.

Option 4 – Try modifying the Windows Security Policy

You can also try to edit the Windows Security Policy as it could help in resolving the error. This Windows Security Policy, when enabled, will not allow non-admin users to log on to the Remote Desktop connection. So if you want to allow non-admin users to use the Remote Desktop connection, then you need to modify this policy. Note that you can only do that if you are the admin of the system yourself.

• Tap the Win + R keys to open the Run utility.
• Then type “secpol.msc” in the field and tap Enter or click OK to open the Local Security Policy.
• After opening the Local Security Policy window, select Local Policies > User Rights Agreement located on the left pane.
• Next, double click on “Allow log on through Remote Desktop Services” located in the right pane.
• And in the next window that appears, select Add user or group.
• After that, type in the username of the intended non-admin user under the “Enter the object names to select” column.
• Once done, click on the Check Names button to fix the username and then click OK to save the changes made.
• Restart your computer.

Option 5 – Use the Group Policy Editor

• Tap the Win + R keys to open the Run dialog box and then type “gpedit.msc” in the field and tap Enter to open the Group Policy Editor.
• Next, navigate to this path: Computer Configuration > Administrative Templates > System > Credentials Delegation.
• Double click on the “Allow delegating default credentials with NTLM-only server authentication” policy setting located on the right pane to edit it.
• After that, shift its radio button to Enabled and click on Show.
• Then type “TERMSRV/*” in the Value box and click OK.
• Now repeat the same for the following policy settings:
  • “Allow delegating default credentials”
  • “Allow delegating saved credentials”
  • “Allow delegating saved credentials with NTLM-only server authentication”

• Once you’re done, restart your computer and see if the problem is fixed.

If you encounter an error message saying, “The ordinal xxx could not be located in the dynamic link library C:/Program Files (x86)/Microsoft VS Code Insiderscode – insiders.exe“ and you see a reference of a missing DLL file, then this indicates that the software is trying to locate the related DLL file, however, it is missing, hence the error. The error mentioned “Ordinal” which refers to the order of a number mathematically, e.g. 1st, 2nd, etc. And in this error message, the ordinal is referring to an Xth file of an XX.DLL file which is missing which is why you’re getting this kind of error. When you get this particular error, it means that your computer is missing the Microsoft Visual C++ Redistributable program. As per the error message, XXX is a number that in turn is the Ordinal. There is also another common error related to Ordinal which says, “The ordinal 12404 could not be located in the dynamic link library mfc90u.dl”. The error message could be referring to any DLL in the message. And since all these DLL files are part of the package, the error changes quite a bit as the Visual Studio looks for that DLL file. To fix this error, here are some suggestions that might be of help.

Option 1 – Try installing Microsoft Visual C++ Redistributable

As pointed out earlier, the error pops up when the Microsoft Visual C++ Redistributable program is missing on your computer. Thus, you need to download it from the official website of Microsoft. Once you’ve downloaded the Microsoft Visual C++ Feature Pack Redistributable Package, install it and then check if the error is now fixed.

Option 2 – Try to install OpenSSL

If you encounter the same error message but it points out that the LIBEAY32.DLL file is missing, then you have to install OpenSSL. In such a case, you will see the following error message:

“Ordinal not found. The Ordinal [Xxxx] could not be located in the Dynamic Link Library Libeay32.dll.”

 Make sure that when you install OpenSSL, you do it into the Windows system directory since the Libeay32.dll file is related to security.

Option 3 – Try to check Windows Updates

There are instances when Microsoft rolls out the framework and related updates via Windows Updates. It could be that an update related to DLL is still pending which is why you need to check Windows Updates. To do so, go to Settings > Update and Security and from there check if there is any pending update. If there is, you need to install that update and then restart your computer if needed.

As you know, Windows Updates are essential for your operating system as it keeps it protected from potential threats, fixes bugs and improves your experience in using Windows 10. However, there are instances when Windows Updates also cause errors and one of them is the Windows Update Error 0x8024000B. One of the causes of this particular Windows Update error is that Windows was not able to read the Update Manifest file which is needed to install the Windows Updates. This means that the operation was canceled by either the service or the user. On the other hand, this error could also occur if you are not able to filter the results. When you encounter this error, you will see an error message that says, “WU_E_CALL_CANCELLED: Operation was canceled”. This indicates that the operation was canceled by the operating system itself. To resolve the Windows Update Error 0x8024000B, here are some suggestions you need to check out.

Option 1 – Try to run the Cleanup (Decline) Superseded updates PowerShell script

The first thing you can do to fix the Windows Update Error 0x8024000B is to run the Cleanup (Decline) Superseded updates PowerShell script. This is actually an easy fix since all you have to do is download and run it from the Microsoft Technet site. Once you’re done downloading and running the file, restart your computer and see if the error is fixed or not.

Option 2 – Try to rename the Spupdsvc.exe file

If the first option didn’t work, you can try renaming the Spupdsvc.exe file which is one of the reasons why you’re getting the Windows Update Error 0x8024000B.

• First, tap the Win + R keys to launch the Run utility.
• Next, type the following command and hit Enter to execute it in cmd:

 /c ren %systemroot%System32Spupdsvc.exe Spupdsvc.old

• The command you entered will rename the troublesome “Spupdsvc(.)exe” file to “Spupdsvc(.)old”.
• Now restart your computer after the command has been executed.

Option 3 – Try to restart various Windows Update-related services and components

You could also try to restart some Windows Update-related services to resolve the Windows Update error. Refer to the following steps to do so:

• Tap the Win + X key combination and select Command Prompt (Admin) to open Command Prompt with admin privileges.
• After opening Command Prompt, copy and paste each one of the commands listed below one by one and tap Enter right after you enter each command.
  • net stop wuauserv
  • net stop bits
  • net stop appidsvc
  • ren %systemroot%SoftwareDistribution SoftwareDistribution.bak
  • ren %systemroot%system32catroot2 catroot2.bak
• Once you’ve entered all the commands given above, they will stop all the Windows Update services that are running on your computer as well as clear the SoftwareDistribution folder, and reset the Catroot2 folder. Now you have to start all these Windows Update services you’ve just stopped by executing the following commands:
  • net start wuauserv
  • net start bits
  • net start appidsvc
  • net start cryptsvc
• After that, restart your computer and try to run the setup again, and see if the error is now fixed.

Option 4 – Try to run the Windows Update Troubleshooter

You should also try to run the built-in Windows Update troubleshooter as it could help you resolve the Windows Update Error 0x8024000B. To run it refer to these steps:

• Go to Settings and then click on Windows Update from the given menu.
• Next, click on the Troubleshoot option and select Windows Update from the given options to run the Windows Update troubleshooter.
• After that, follow the next on-screen instructions and wait until the process is completed, and check if the Windows Update Error 0x8024000B is fixed or not.

What Is Error 103?

Error 103 is an error that is usually encountered by those who use Google Chrome. This error is usually generated because of a conflict arising between Google Chrome and the antivirus program running on the user’s computer. Primarily, error 103 is an incompatibility issue. It is not critical in nature. However, since it will disrupt the smooth functioning of the browser, it is strongly advised to rectify this error that is generated due to any temporary conflicts between the logic of the two programs namely Google Chrome and antivirus. In layman's terms, it would be only justified to say that this error has a lot to do with the way programs react to each other in real-time.

Solution

Error Causes

When the error is displayed to the user, it usually states something like ‘chrome error 103 connection aborted’, ‘chrome error 103 err_connection_aborted’ or ‘Error 103 (net: ERR_CONNECTION_ABORTED): Unknown error. This begs the question, what triggers this error? Here it is important to understand that Google Chrome constantly applies to upgrade. In most instances, the upgrades almost go unnoticed. In the meanwhile, there are other programs running on any system such as firewall, Antispyware, or antivirus programs. All such programs govern the functionality of the web browser. Now, when the web browser attempts to update and any programs on the system view the update as a threat, the connection to the internet will be terminated. It is also important to understand that these programs will keep you from upgrading or from doing anything with your browser.

Further Information and Manual Repair

Before we move on to the discussion of fixing the underlying causes for error 103, it is important to understand all those programs that are most likely to generate this error. A list of all such programs is outlined below as follows.

• Kaspersky Pure 3.0
• Kaspersky ONE
• Kaspersky small office security 2013
• Kaspersky internet security 2013
• Kaspersky antivirus 2013

A downside associated with error 103 is that it won’t disappear on its own. That’s why it is important to make some manual changes as there are no tools available online to rectify this error automatically. Follow the steps listed below to easily fix the problem.

• Click on the Start button.
• In the search box, enter ‘expand.exe’.
• Right-click on the file that appears and select the option ‘Open Folder Location’.
• Now, copy the file and paste it at the destination ‘C:\Windows\System32’.
• If you are not able to find the file, it is advised you copy it from Windows Installation Disk.
• Now, click on the ‘Start’ button again.
• Find and select ‘Run’.
• Now enter ‘C: ’ in the search box and press Ok.
• Now right-click anywhere on the screen, select new, and then select folder.
• Rename this folder. Change the name from ‘New Folder’ to ‘Temp’.
• Now go to the Start button again.
• Select ‘Run’ once again.
• Type ‘cmd.exe’ in the command prompt and press Ok.
• Now type Command. Press enter.
• Now type this code as it is: ‘set TMP=C:temp’ and press enter.
• Now restart the browser.
• If it fails, install Google Chrome once again.
• Just make sure everything is in sync to avoid any data loss.

Error Code 0x80070652 – What is it?

Error code 0x80070652 occurs when Windows users attempt to upgrade their operating system while another program is in the process of being downloaded. It may also occur due to problems related to previously failed update attempts within Window Update. When this Windows 10 upgrade occurs, Windows users fail to access the version of Windows they are attempting to download. Instead, a message box occurs stating that error code 0x80070652 has occurred on the device. If this error message is not rectified, it could give birth to other Windows 10 errors such as error code 0x80072EE2.

Solution

Error Causes

Error code 0x80070652 may result from Windows 10 users attempting to download another program while upgrading their operating system. It may also be caused by an issue related to previous installations of updates. For instance, in some cases, your previous installation of the Windows process may have been interrupted or it was simply not completed properly. This causes any other upgrade process that follows to result in error code 0x80070652.

Further Information and Manual Repair

But what can be done in such a situation to resolve the error code? Windows users have several options available. For instance, they can wait on any additional program that may be in the process of downloading to complete the process before attempting to upgrade Windows. They may also troubleshoot problems related to any failed updates or select a system restore point in which the error code was not present.

The manual repair methods Windows 10 users choose may involve any of the solutions mentioned previously. The choice is largely dependent on the user and his determination to fix the error code. However, note that automated tools or Windows repair technicians may also provide solutions to PC issues like error code 0x80070652.

Method One: Verify and Troubleshoot Failed Upgrades

Since previously failed updates within Windows Update can lead to the occurrence of error code 0x80070652, Windows 10 users will need to verify which of these failed updates occurred by checking the history section of the Windows Update tool. Once you’ve been able to verify that failed updates have occurred in the recent past, you’ll need to troubleshoot these problems to rectify the error code. Follow the instructions below to check for updates that have failed to install properly via Windows Update.

• Step one: Type Windows Update in the Search box near Start Menu
• Step two: Select Windows Update settings
• Step three: Select Update history
• Step four: Review updates from the most recent to least recent to see which updates have failed
• Step five: Click failed updates for more details and troubleshoot accordingly.

Once you’ve completed the troubleshooting of any updates which failed, proceed by rebooting your device. You may then reattempt to upgrade to the latest version of Windows 10 once no other program is in the process of being downloaded.

If the problem causing error code 0x80070652 was related to failed updates of the past, these issues will likely be resolved once you successfully troubleshoot them. However, if the error code reoccurs, apply the next manual repair solution mentioned in this article.

Method Two: Download Updates Manually via Microsoft Download Center

Another option available to users is simply downloading updates manually by visiting the official Microsoft website, specifically the Windows section which provides downloads. To successfully complete this process, ensure you look for stand-alone packages of these downloads available on the website. You will need to know the Microsoft Knowledge Base (KB) article number related to the specific update(s) which failed.

Once a Windows user has verified the KB article number of the specific update, download it from the Microsoft website, then select Run to install the update. Reboot your PC, then check Windows Update to see if you are able to successfully complete the Windows 10 upgrade.

If the upgrade fails, you may need to implement the next manual repair method as is mentioned below.

Method Three: Use Windows System Restore

One of the best options for Windows 10 users facing certain PC problems is to apply System Restore. This allows them to reset their machine for a period of time in which the problem was not present. This is known as the restore point. To apply this manual repair method, follow the steps below.

• Step one: In the search box beside the Start Menu, type System Restore
• Step two: Select Create a restore point
• Step three: Select the System Protection tab then Configure or Create
• Step four: Provide details regarding a system restore point of your choice
• Step five: Select Create, then OK.

Method Four: Download an Automated Tool

If you wish to always have at your disposal a utility tool to fix these Windows 10 and other related issues when they do arise, download and install a powerful automated tool.

When it comes to computer peripherals first thing that comes to people's minds is probably Mouse and Keyboard. Also when discussing peripherals brands, Razer is not a stranger and over the years it has built its name and cult following. Razer’s mechanical keyboards have been always in the upper field of quality and trust from users and Huntsman is no different.

Tech specifics of Huntsman keyboard

1. Mechanical optical switches Razer has introduced their new optical technology switch with this keyboard. These switches are faster and more accurate than typical mechanical switches and if tests are to be believed this is the fastest keyboard currently on the market.
2. Multi-functional digital dial A multi-function digital dial with three tactile media keys gives you instant access to everything from brightness to volume in seconds. All programmable and customizable through Synapse 3, so you can set your preferred configurations right at your fingertips.
3. 10-key rollover Anti-ghosting technology that enables 10-key simultaneous presses at the same time
4. 4-side underglow with Razer chroma Go crazy and personalize lighting effects any way you want with a full 4-side underglow and 38 customization zones. Powered by Razer Chroma

Feel and noise

In the department of noise, well it is the mechanical keyboard so naturally, it will be louder than membrane ones but in terms of comparing it to other mechanical keyboards it is within the same noise range, maybe just a tiny bit silenced. The keyboard comes with 2 different types of switches, purple clicky ones that are louder and have that *click* sound for sound feedback, and red ones, that are not equipped with clicky sound but are linear providing slightly faster performance. If you choose the Huntsman elite model of the keyboard it will come with a nice hand resting mat that is very comfortable and feels right. Using a keyboard feels like using a Razer keyboard, it is responsive and gives that superior mechanical feeling.

Conclusion

Razer Huntsman mechanical keyboard is not the cheapest nor the best on the market but it is the fastest one out. It is in the top tier of keyboards and worth the investment.

As you know, games with good graphics and fast play are definitely resource-intensive and can consume a lot of storage space on your computer. Because of that, they have to be compressed before it gets downloaded to your computer and then unpacked to the hard drive before it gets installed. However, if an error occurs in your computer’s RAM during the installation process or if your hard disk does not have enough memory to handle the process, then you might encounter the isDone.dll error which states:

“An error occurred when unpacking, Unarc.dll returned error code -1, ERROR: archive data corrupted (decompression fails).”

If you encounter the isDone.dll error message on your Windows 10 computer, then read on as this post will show you how you can fix it. This error has something to do with the incomplete installation of PC games or files of larger size. The ISDone.dll error appears due to faulty Unarc.dll file residing in the System32 folder on 32-bit operating systems and the SysWOW64 folder on 64-bit systems. So, if you see this error message, then, it means your computer was not able to read installation archive files.

What is Unarc.dll file?

Unarc.dll is a dynamic link library for Windows. Some applications or games require this file to function properly. So, if it goes missing or, an error occurs when you start a game or an application, you may get various kinds of errors. ISDone.dll error while playing games on PC

Option 1 – Try to reinstall the game

The isDone.dll error could also be caused by the installation of an unknown application. Or it could also be caused by an outdated or corrupted application. In other words, if the game you are trying to install is broken or corrupted, then it’s no wonder why you’re getting the isDone.dll error. To fix this, make sure that you download the latest updated version of the game and then try to install it again and see if the problem is resolved or not.

Option 2 – Try to re-register the .dll file using the Regsvr32 tool

• The first thing you have to do is to locate the DLL file named dll on your computer and rename it to Unarc-bak.dll.
• Next, copy the Unarc.dll file from another well-functioning computer and save it on your desktop.
• After that, move the DLL file you just copied to the System32 folder if you are using a 32-bit operating system, or the SysWOW64 folder if you are using a 64-bit operating system.
• Now you have to register the new DLL file and you can do that using Windows PowerShell.
• Open Windows PowerShell and then execute this command if you have placed the DLL file in the System32 folder: regsvr32 %systemroot%System32unarc.dll
• On the other hand, if you have placed the DLL file in the SysWOW64 folder, then execute this command: regsvr32 %systemroot%SysWOW64unarc.dll
• Once you’re done, a message will be displayed saying that the DLL file was registered.
• Restart your computer and check if the problem is now fixed.

Option 3 – Troubleshoot the isDone.dll error in a Clean Boot State

You can also troubleshoot the isDone.dll error in a Clean Boot state. It could be that there are some third-party applications in your computer that're preventing the application from getting installed and to isolate this possibility, you need to boot your computer in a Clean Boot State and then try installing the program again. Putting your computer in this state can help you identify which program is the culprit and thus isolates the problem. In a Clean Boot state, your computer will start using only the pre-selected minimal set of drivers and startup programs. Note that you have to disable and enable one process at a time.

• 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.)
• After you’ve set your computer into a Clean Boot State, make sure that you’re signed in as administrator and then try to install the application again.

Option 4 – Try updating or reinstalling your Graphics drivers

Updating or reinstalling the Graphics drivers in your computer can also help in resolving compatibility issues between the operating system and the driver that might have caused the isDone.dll error.

• First, boot your computer into Safe Mode.
• After that, tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. From there, look for the Display Adapters and click on them.
• After that, right-click on each entry under the Display Adapters and select the “Uninstall Device” option from the menu.
• Now restart your computer.
• After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.

Note: You also have the option to go directly to the website of your graphics card manufacturers like NVIDIA, Intel, or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it.

Option 5 – Try scanning your computer using Windows Defender

The isDone.dll error might also be infected with malware or virus and to eliminate it, 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.

If you are trying to save a file in a PDF format on your Windows 10 computer but then the PDF text content in an Adobe file suddenly disappears, then read on. This post will give you more insight into this issue. This kind of issue is rare and mostly occurs in forms that you can fill upon. In such a case, the text you enter in the form vanishes right after you click the Save button. One of the benefits of working with PDF files is that it has the ability to compress high-quality files to relatively small file sizes. This is really useful especially when you are saving hard drive space and you’re working with limited storage resources. However, these files can contain layered content if they are created from layered documents using applications like Adobe InDesign. Consequently, a single page of the PDF file can contain different layers with different content. So if you try to save or print a PDF file that contains layered content, the elements will disappear from the PDF. To resolve this issue, you can try to merge or flatten the file since it will help keep the changes in the PDF file. On the other hand, you can no longer make any alterations or form data once you flatten the file. Another thing to keep in mind is that merging or flattening the file can’t be undone so you might want to save another copy of the file before you proceed.

Option 1 – Print to PDF

• First, you have to open the desired PDF file and tap the Ctrl + P keys to open the Print dialog box.
• After that, select the “Microsoft Print to PDF” option as the printer.
• Once the action is confirmed, it will regenerate another version of the PDF file with the default settings and merge all the existing layers into a single layer.
• On the other hand, you can also click on the “File” menu of the PDF file and select Print.
• From there, click on the Print button and select “PostScript (*.ps)” as the “Save as” type to save a PostScript copy of the original PDF file.
• Once you’re done, double click on the .ps file to open the file in the Adobe Distiller which will flatten the file automatically and convert it to a PDF file with only one visible layer.

Option 2 – Save the PDF file as an Optimized PDF file

If you are using the Acrobat Reader Pro version such as the Acrobat Pro, Foxit, and so on, you can try to flatten the layers by saving the PDF file as an Optimized PDF file. Refer to these steps to do so:

• Select File > Save as > Optimized PDF.
• Next, select the Transparency checkbox from the Settings window that opens.
• Then click on the Save button to apply and save the changes made. After that, the PDF text content should not disappear when you try to save a file on your Windows 10 computer.

If you suddenly encounter the DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL Blue Screen error on your Windows 10 computer along with the error codes, 0x000000D5, 0xb10BBD9E, 0x0D82DA24, 0Xfecd479D, 0x779827CB then read on as this post will provide you some troubleshooting tips that could help you resolve the BSOD error. Getting this kind of BSOD error means that a driver has referenced memory that was freed earlier and it could also mean that the Driver Verifier Special Pool option has caught the driver accessing memory which was freed earlier. Follow the given options below to fix the DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL BSOD error.

Option 1 – Use the Driver Verifier Manager

The Driver Verifier Manager is another tool in Windows that could help you fix driver-related issues.

• Type in the keyword “Verifier” in the Cortana search box to search for Verifier in Windows 10.
• After that, select the option “Create custom settings”.
• Make sure that you have checked everything except the options “DDI compliance checking” and “Randomized low resources simulation”.
• Next, select the option “Select driver names from a list” option.
• Afterward, you have to select all the drivers from any unofficial or third-party provider. To simply put it, you have to select all the drivers that are not supplied by Microsoft.
• Then click on the Finish button.
• Open Command Prompt as administrator and execute this command – verifier /querysettings
• The command you just executed will display the Driver Verifier settings so if you see any of the flags enabled boot your Windows 10 PC into Safe Mode.
• Open the Command Prompt as admin again and run this command – verifier /reset
• The command will reset the Driver Verifier. Once the process is done, restart your PC and check.

Option 2 – Try updating SSD firmware

If you have installed SSD on your computer recently and you have started getting the DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL Blue Screen error since then you may have to update the SSD firmware. To fix this, you can download the Intel Solid-State Drive Toolbox from the official website. This toolbox is compatible with Windows 10 and Windows 7 and later versions.

Option 3 – Try running the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL. It can be found in the Settings Troubleshooters page. To use it, refer to these steps:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

Option 4 – Try running Microsoft’s online Blue Screen Troubleshooter

If running the built-in Blue Screen Troubleshooter didn’t work, you can also try running Microsoft’s online Blue Screen Troubleshooter. All you have to do is go to Microsoft’s website and from there, you will see a simple wizard that will walk you through the troubleshooting process.

Option 5 – Try to reinstall or update device drivers of recently installed hardware

If the first few options 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 6 – Try disabling Hardware Acceleration

You might want to disable Hardware Acceleration system-wide or for a particular program like Google Chrome and see if it resolves the DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL BSOD error