Logo

Disabling the Recently Opened Files in Windows

The Windows 10 operating system comes with a user-friendly interface as well as better security features compared to its previous versions. One of these new features is the “Recently Opened Files” feature which displays all the files you’ve opened recently in File Explorer. Although it might seem useful, some users see this as a privacy concern especially if there are other users that use the same computer. If you are one of these users, read on as this post will guide you on how you can disable the “Recently Opened Files” feature in Windows 10.

There are three ways you can disable the “Recently Opened Files” feature. You can manually clear the recent files, or disable the feature via Control Panel. You can also do it using the Group Policy Editor.

Option 1 – Manually clear the recent files

The first thing you can do is to clear the recent files manually. Since the information about the recently opened files is stored in the form of cached data, you can locate this data and delete it manually, from time to time. To do that, follow these steps:

  • Tap the Win + R keys to open the Run utility and copy this address in the field: %AppData%MicrosoftWindowsRecent
  • Next, tap the Ctrl + A keys to select all the items and then tap the Shift + Delete keys simultaneously.
  • After that, a prompt will appear where you have to click on Yes. This will delete all the recently opened files in the File Explorer the next time you open it.

Option 2 – Disable the feature via Control Panel

The next option you can try to disable the feature is via Control Panel. Refer to these steps to do so:

  • First, click on the Start Menu button and select the Settings icon.
  • After that, click on Personalization and then on Start located on the left pane.
  • Next, scroll down until you see the “Show recently opened items” in Jump Lists on the Start or the Taskbar and click on it and then toggle it off.

Option 3 – Disable the feature using the Group Policy Editor

If you are using the Windows 10 Pro version, then you have access to edit the functions in the Group Policy. The Group Policy function has the option that can disable all the default services of Windows 10. Note that in this step, you will permanently disable the “Recently Opened Files” feature. So before you proceed, make sure that you really want to disable this feature permanently and not in the meantime.

  • Tap the Win + R keys to open the Run dialog box and type “gpedit.msc” in the field and click OK or tap Enter to open the Group Policy Editor.
  • Next, on the left side pane, click on the “User Configuration” option and then click the “Administrative Templates” option.
  • After that, select the “Start Menu and Taskbar” option and select the “Don’t keep the history of recently opened documents” option in the right pane.
  • Now double click on this option and check the “Enabled” option and then click on Apply and OK buttons to save the changes made.

Do You Need Help with Your Device?

Our Team of Experts May Help
Troubleshoot.Tech Experts are There for You!
Replace damaged files
Restore performance
Free disk space
Remove Malware
Protects WEB browser
Remove Viruses
Stop PC freezing
GET HELP
Troubleshoot.Tech experts work with all versions of Microsoft Windows including Windows 11, with Android, Mac, and more.

Share this article:

You might also like

Fix The selected boot device failed in Windows
If you suddenly receive an error message that says, “The selected boot device failed, Press <Enter> to Continue” during an installation on your Windows 10 computer, you should know that this kind of error can occur when you use a USB stick as well as a DVD Disk to boot from. This error indicates that some settings inside your BIOS are not compatible with the bootable device that you have created. Note that fixing this kind of error does not vary from device to device at all. All you have to do is change some settings in the BIOS and create a proper bootable disk. Follow the options given below to fix the “The selected boot device failed, Press <Enter> to Continue” error. The options below do not have to be necessarily followed in the same sequence since you can create a bootable USB drive before you change some settings in the BIOS.

Option 1 – Disable the Secure Boot in the BIOS

Disabling the Secure Boot in the BIOS settings is definitely recommended to resolve the issue. To disable Secure Boot, here’s what you have to do:
  • First, boot your computer into Windows 10.
  • Next, go to Settings > Windows Update. From there, check if there is anything that you have to download and install if you see any available updates. Usually, OEMs send and update the list of trusted hardware, drivers, and operating systems for your computer.
  • After that, go to the BIOS of your computer.
  • Then go to Settings > Update & Security > Advanced Startup options. If you click on Restart Now, it will restart your computer and give you all the advanced options.
  • Next, select Troubleshoot > Advanced Options. As you can see, this screen offers you further Options including System Restore, Startup repair, Go back to the previous version, Command Prompt, System Image Recovery, and UEFI Firmware Settings.
  • Select the UEFI Firmware Settings which will take you to the BIOS.
  • From there, go to the Security > Boot > Authentication tab where you should see Secure Boot. Note that every OEM has its own way of implementing the options so it varies.
  • Next, set Secure Boot to Disabled and set Legacy Support to On or Enabled.
  • Save the changes made and exit. Afterward, your computer will reboot.

Option 2 – Make a proper bootable USB Drive/Stick

To make a proper bootable USB drive, you need to use the Windows Media Creation tool. The Media Creation tool in Windows allows you to use the ISO installation file to make a bootable device that you can use to install Windows on your PC. Note that this is kind of different from the usual installation process as it could erase your computer’s current settings and data on the primary drive. Thus, before you proceed, you need to backup all your data into some removable drive and then use the Media Creation Tool to make a bootable drive.
  • After making the bootable drive, you need to plug it into your computer and then reboot.
  • Next, tap the F10 or Esc key to open the boot options.
  • Now set the boot priority of the removable drive the highest. Once the setup comes forth, follow the next onscreen instructions and install Windows without any problems.
Read More
The request failed due to a fatal device hardware error
When you are copying some files from your computer to your hard disk and vice versa or when you have several disks connected to your Windows 10 computer and you suddenly receive an error message saying, “The request failed due to fatal device hardware error”, then this means that there is some issue with the hardware of your computer. This issue might be caused by various reasons but whatever they may be, this post will guide you on how you can fix the “The request failed due to fatal device hardware error”. To fix the error, here are some suggestions that could help.

Option 1 – Check for any hard disk errors

  • On your desktop, right-click on the “This PC” or computer icon and then select Manage to open the Disk Management. Here you get to check your drive’s health.
  • Next, click on Disk Management on the left side panel.
  • From there, check the state of your drives. If it shows that all your partitions are healthy then it means all is good and that the problem may have something to do with some physical issues with your hard drive.

Option 2 – Run the CHKDSK utility

When it comes to some issues concerning the hard drive or removable devices, there is a utility in Windows that might help which is called “chkdsk”. This error check utility can help with several issues in the system including “The request failed due to fatal device hardware error”.
  • Tap the Win + S keys to open the Search box.
  • Then type “command prompt” in the field and from the search results that appear, right-click on Command Prompt and select “Run as administrator”.
  • After opening an elevated command prompt, copy and paste the following command and hit Enter:
CHKDSK [volume [[path] filename]] [/F] [/V] [/R] [/X] [/C] [: size]]
Note: In the command given above, “[/F]” will try to fix the system errors while “[/R]” will be the one to fix the bad sectors.
  • Now if you are prompted to run CHKDSK after your reboot your PC, just tap Y and reboot your PC.
  • If CHKDSK is not able to find any errors, tap the Win + E keys and navigate the access window. From there, right-click on the concerned drive and click on Properties.
  • After opening Properties, click on the tab Tools and then click on the “Check” button under the Error-checking section.
  • Wait until the process is completed and then restart your computer

Option 3 – Verify the hard drive using SMART attributes

In case you don’t know, Windows has a built-in feature of SMART analysis which analyzes the hard drive/SSD and checks all the parameters by performing some minor operations. To use it, follow these steps:
  • Tap the Win + S keys and type “command prompt” in the field then right-click on the related search result and select the “Run as administrator” option.
  • After opening Command Prompt as admin, type the “wmic disk drive get status” command and hit Enter.
  • You should get a result after that, and if you see that it’s “normal”, proceed to the next option below.

Option 4 – Format your hard disk

You can try formatting your drive since this problem also occurs on removable hard drives. In addition, if your drive is not properly initialized, this error will really pop up. Thus, you need to make sure that the hard drive is initialized and that the correct partition style is selected.
  • 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.
Read More
STOP 0x00000050 - An Easy Fix Guide

Stop 0x00000050 is an error code that is popularly known as the Blue Screen of Death (BSoD) error. This error occurs when Windows crashes on your system. Stop 0x00000050 error is displayed in a blue screen which is why it is called the BSoD error.

The error message appears in the following form:

Stop 0X00000050 (parameter1, 0, parameter3, parameter4)

PAGE_FAULT_IN_NONPAGED_AREA”

However, the parameters within the Stop 0x0000005 error message sometimes vary depending on your PC configuration.

Solution

Restoro box imageError Causes

The most common causes of the Stop 0x0000005 error are:

  • Hardware malfunctioning
  • Overheating of the components
  • Installation of a faulty device driver
  • Incompatible DLL files
  • Corrupt Registry
  • Spyware and Virus Infection

Whatever the cause may be, the Stop 0x00000050 error message is alarming and should be fixed at the earliest as it indicates major system stability problems that can often lead to data loss and system corruption.

Further Information and Manual Repair

To fix and repair the Stop 0x0000005 error you don’t always have to hire an IT professional. In fact, fixing this error is quite easy and you can do it yourself regardless of whether you have a good know-how of computers or not.

So, let’s get started! Here are some the easy DIY solutions to fix the Stop 0x0000005 error:

Sometimes this error may occur due to a temporary issue like overheating of the computer components. When this happens all you need to do is switch off the computer and allow the components to cool down. Try starting up your computer after a couple of hours. If the blue screen of death does not occur again, then this means there is nothing to worry about and the problem is resolved.

However, if the error appears again on your screen, then you need to try something else to solve and fix this error on your PC. If the cause of the error is a faulty device driver, then it is advisable to disable and remove it. Try updating the latest version of the faulty device driver. Using updated software helps ensure your PC keeps running smoothly.

If the cause of the Stop 0x0000005 error code is your system's exposure to viruses and spyware, then you must immediately download a powerful antivirus program. After you download it, scan for viruses on your system. Once the scanning is complete, you will see a scan report showing viruses on your PC. Delete all of them and click on repair.

Furthermore, you can also add more RAM to prevent and fix the Stop 0x0000005 error message on your computer. This solution is suitable when you try to run a program on your PC and you get this error message.

Read More
A Quick Guide to Repair User32.dll Error Code

User32.dll Error Code - What is it?

User32.dll is a Dynamic Link Library file. Windows stores instructions for graphical elements such as dialog boxes and Windows in this file. This file is a crucial file, necessary to run Windows operations. If this file is damaged, deleted, or removed from the system you may not be able to run the programs on your system that use and share the User32.dll file thereby causing you inconvenience. The User32.dll file error is displayed in the following format:

“This application has failed to start because USER32.dll was not found. Reinstalling the application may fix this problem.”

Or

“[Program] illegal system DLL relocation”

Program here refers to the name of a program that caused the User32.dll error message.

Solution

Restoro box imageError Causes

User32.dll errors are triggered by the following reasons:
  • Missing and damaged .dll files
  • Viral infection
  • Registry corruption
User32.dll error is also referred to as C0000135 blue screen of death error. When the User32.dll error occurs it not only locks you out of your desired program but also turns your computer screen blue. If the error is not repaired timely it may expose your PC to serious threats such as abrupt system shutdowns, system failure, and crash.

Further Information and Manual Repair

To resolve the User32.dll error on your PC, try the following solutions:

1. Reinstall Programs Causing User32.dll errors

Sometimes User32.dll error may occur due to missing DLL files.  This happens when you delete a program from your PC and accidentally the DLL file also gets deleted which is shared by other programs on your system. Therefore to resolve this first find out what programs on your system use User32.dll to load and run on your system. To do this use the Tasklist command-line tool. It displays the names of all the programs that currently use the User32.dll file. After this, reinstall the programs that use User32.dll files on your system. This will hopefully resolve the error.

2. Install and Run Restoro

If it doesn’t, then this probably means that the damage is deep-rooted. It is related to the damaged DLL files, registry corruption, or viral infection. To resolve all of these causes in one go, it is best to download Restoro instead of downloading 3 different software to resolve each cause for the error separately. This is basically an advanced, innovative, and multi-functional PC repair tool embedded with multiple powerful utilities including a registry cleaner, and a system optimizer. It is a one-stop solution for all your PC-related problems including the User32.dll error. The registry cleaner wipes the clutter and obsolete files damaging the hard disk and simultaneously repairs the DLL files and the registry. The antivirus feature removes all the viruses on your system while the system stability utility boosts the PC speed significantly. It is safe, user-friendly, and compatible with all Windows versions including Windows Vista, XP, Windows 7, 8, 8.1, and 10. Click here to download Total System Care to resolve the User32.dll error right away.
Read More
Chrome update failed error 3, 4, 7, 10, etc
If you find it hard to update Google Chrome to its latest version and each time you try to do so it keeps on failing, worry not for this post will guide you in fixing a list of Google Chrome Update errors. Even though there are a lot of error codes around Chrome, these are only caused by issues with the update. Here are some of the errors you can encounter when updating Google Chrome:
  • Update failed: You can encounter this error when the Updates are disabled by the administrator.
  • Update failed with
    • Error 3 or 11: When Chrome’s inbuilt updater fails to find the Update server to download the latest version.
    • Error 4 or 10: This happens while checking for updates with the message “Update check failed to start”
    • Error 7 or 12: This occurs when the download fails while checking for updates.
  • Windows OS version is not supported.
  • Google Chrome may not be able to keep itself updated.
  • Any other errors that mention that “Update failed”
Since these aforementioned error codes are related to “Update Failure”, then they have common solutions and here they are:

Option 1 – Restart your computer

You need to restart your computer first and then try updating Chrome again. There are times when it’s only a temporary issue that can be fixed by simply restarting your computer.

Option 2 – Try checking antivirus programs, firewall, and parental control settings

If you have antivirus programs, a firewall installed in your computer, as well as parental controls, then any of these could be blocking you to download anything, including the update for Chrome. This is why you have to double-check and make sure that software updates aren’t being blocked by these programs. On the other hand, you can also try running the Network Troubleshooter as it can help you resolve any DNS or connectivity issues. To use it, follow the steps below.
  • 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.

Option 3 – Try to remove Proxy

Removing the Proxy might also help you in fixing the Chrome Update errors. 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 4 – Try to reset Winsock, TCP/IP & Flush DNS cache

Resetting Winsock, TCP/IP, and flushing DNS might help in resolving the Chrome Update errors just 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.
  1. netsh winsock reset – type in this command to reset Winsock
  2. netsh int ip reset resettcpip.txt – type in this command to reset TCP/IP
  3. ipconfig /flushdns – type in this command to flush the DNS cache
  • Next, restart your PC and check if the problem’s fixed.

Option 5 – Try to run the Chrome Cleanup tool

You might want to run Google Chrome’s built-in Malware Scanner & Cleanup tool as it could also help in getting rid of any unwanted ads, pop-ups, and even malware, as well as unusual startup pages, toolbars, and anything else that might overtake the network and could affect the performance of the browser.

Option 6 – Get rid of any conflicting browser extensions

  • Open Chrome and press Alt + F keys.
  • Go to More tools and click Extensions to look for any suspicious browser extensions or toolbars.
  • Click the Recycle bin and select Remove.
  • Restart Chrome and press Alt + F keys again.
  • Proceed to On Startup and mark Open a specific page or set of pages.
  • To check if the browser hijacker is still active, click Set pages, if it is active, overwrite the URL.

Option 7 – Reset Google Chrome

Resetting Chrome can also help you get rid of the error. Resetting Chrome will restore its default settings, disabling all the extensions, add-ons, and themes. Aside from that, the content settings will be reset as well and the cookies, cache, and site data will also be deleted. To reset Chrome, here’s what you have to do:
  • Open Google Chrome, then tap the Alt + F keys.
  • After that, click on Settings.
  • Next, scroll down until you see the Advanced option, once you see it, click on it.
  • After clicking the Advanced option, go to the “Restore and clean up option and click on the “Restore settings to their original defaults” option to reset Google Chrome.
  • Now restart Google Chrome.
Read More
Domain Users Sign in using Biometrics
The use of Biometrics is supported by Windows 10. Aside from that, it also supports PIN, password, picture password on all computers and if your computer has the proper hardware, Windows 10 also supports facial scanning, iris scanning, and even fingerprint scanning. You can see all these exciting features inside Settings > Accounts > Sign In Options. On the other hand, you can’t really expect to make use of all the above-mentioned features since it depends if the hardware is available to support them. One of the most interesting features is the use of Biometrics which is really useful in workplaces and so this post will show you how you can enable or disable the Domain Users Sign In on Windows 10 using Biometrics via Registry Editor or Group Policy Editor. But before you go on, you need to create a System Restore Point first since the modifications you’re about to do might affect the functioning of your computer. So in case something went wrong, you can always undo the changes you’ve made.

Option 1 – via Registry Editor

  • Tap the Win + R keys to open the Run dialog box.
  • Next, type “Regedit” in the field and hit Enter to open the Registry Editor.
  • After that, navigate to the following registry path:
HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftBiometricsCredential Provider
  • From there, right-click on the right-side panel and click on New > DWORD (32-bit) Value.
  • And then set the name of the newly created DWORD as “Domain Accounts”.
  • Afterward, click on “Domain Accounts” and set its value to “1”. This will allow the domain users to sign in to Windows 10 using Biometrics. While the value of 0 will disable the domain users sign in to Windows 10 using Biometrics.
  • Exit the Registry Editor and restart your computer for the changes to take effect.

Option 2 – via Group Policy Editor

  • Tap the Win + R keys to open the Run dialog box.
  • Next, type “gpedit.msc” in the field and hit Enter to open the Group Policy Editor.
  • After that, navigate to the following setting:
Computer Configuration > Administrative Templates > Windows Components > Biometrics
  • Then double click on the following entries located on the right-side panel and set the radio button to Enabled on all of them.
    • Allow the use of Biometrics.
    • Allow users to log on using Biometrics.
    • Allow domain users to log on using biometrics.
  • Now exit the Group Policy Editor and restart your computer to apply the changes made properly.
Read More
How to Fix Windows 10 Upgrade Compare Exchange128 Error Message

Compare Exchange128 error – What is it

Some Windows 7 and Windows 8.1 users reported experiencing a Compare Exchange128 error when trying to upgrade to Windows 10. The error reads, “You can’t install Windows 10 because your processor doesn’t support CompareExchange128”. In order to upgrade to Windows 10 (64-bit), the CMPXCHG16B instruction must be present. If you receive this error, this mostly means that your CPU doesn’t have the CMPXCHG16B instruction.

Solution

Restoro box imageError Causes

The CompareExchange128 error normally occurs due to two possible reasons:

  • CPU lacks CMPXCHG16b Instruction
  • Old & Outdated BIOS – Even if your CPU has the CMPXCHG16b instruction, the CompareExchange128 issue can still occur if you have an older BIOS.

Further Information and Manual Repair

One main requirement to upgrade to Windows 10 is for your CPU to have the CMPXCHG16b instruction. You also need the right BIOS version to guarantee a smooth installation. See below on how to manually fix this issue.

NOTE: If you don’t feel confident using the manual methods listed below, it’s highly advisable to get help from an expert technician. If you don’t know someone, you can also use an automated tool to fix this.

Before performing any fixes, try to determine first if the cause of the error is due to your CPU lacking the CMPXCHG16b instruction. You can use a CPU Info tool that provides complete details about your processor, memory, and motherboard. If you’re looking for more in-depth information, you might also try command-line utilities. But, the safest and easiest way to check this is by simply searching online. Try using the search query: <CPU Model> CMPXCHG16b

Method 1 – Update your BIOS

This method will download the latest BIOS from your motherboard’s manufacturer. This makes sure your CPU has the CMPXCHG16b instruction needed to complete the Windows 10 64-bit installation. To update your computer’s BIOS, complete the following steps:

  1. Determine first the current BIOS you have on your computer. Open System Information Windows app and type msinfo32 in the search bar. The BIOS version will appear under the processor speed. Record it somewhere.
  1. Go to the support page of your motherboard’s manufacturer. Find if there’s any update on the BIOS that you’re currently using. If you find one, download the BIOS update file available. Make sure that you’re looking into the right model and you download all the necessary documentation. Otherwise, the BIOS update might not work.
  1. Update your BIOS. Most BIOS update steps are straightforward. Just make sure to follow the steps provided.

Method 2 – Install Windows 10 32-bit version

If updating the BIOS doesn’t work, what you can do is install a 32-bit version of Windows 10 instead of the 64-bit version. Here’s how to do this:

  1. Download and install the 32-bit version of Windows you currently have. If you have a Windows 7 64-bit version, get the 32-bit version of Windows 7. The same goes for Windows 8.1. When you do this, you might want to back up your files first. Remember that installing the 32-bit version works like other installations, and could delete some of your files.
  1. After installing the 32-bit version, go to Updates and install all the necessary updates. This includes upgrading to Windows 10 if you’re asked to.
  1. When you installed the Windows 10 upgrade, you’ll now have the Windows 10, 32-bit version installed. This will be the version activated on Microsoft servers. Despite this, the activated version stored is only applicable to your computer’s hardware, not the version of Windows 10.
  1. Download Windows 10, 64-bit version.
  1. Prepare an empty DVD or USB flash drive. Use Creation Media software then click the Create Installation Media for Another PC option.
  1. Install the 64-bit Windows 10 version you downloaded from Step 4. Make sure not to put anything when you’re asked to input the serial number.
  1. Once the installation is complete, you’ll have the 64-bit version of Windows 10.

Method 3 – Buy a new processor/motherboard

If the above two methods don’t work, there’s a great chance that this error occurs because of an outdated processor/motherboard. Your next possible solution is to buy an updated model that’s fully compatible with 64-bit Windows 10.

Method 4 – Download an automated tool

If all else fails, you might want to consider using this powerful automated tool to quickly fix the problem and any other computer-related issues.

Read More
Fix wdf01000.sys BSOD Error on Windows
If you encounter a Blue Screen error that points to the Wdf01000.sys file, then this post might be of help. Wdf01000.sys is a file related to the Windows Driver Framework which is the one that manages the system drivers. So if this file ends up being corrupted, the drivers would start to cause trouble in the system which would lead to a Blue Screen of Death error eventually. There are lots of error descriptions that are associated with the Wdf01000.sys file such as:
  • DRIVER_IRQL_NOT_LESS_OR_EQUAL
  • System_Thread_Exception_Not_Handled
  • Page_Fault_In_Nonpaged_Area
  • System_Service_Exception
  • Kmode_Exception_Not_Handled
  • DRIVER_VERIFIER_DETECTED_VIOLATION
Although the troubleshooting steps you must take depends on the kind of BSOD error you are getting, there are a couple of options you can try to resolve the Blue Screen errors related to the Wdf01000.sys file. Refer to the options given below.

Option 1 – Try running the DISM tool

You can try running the Deployment Imaging and Servicing Management or DISM tool to fix the Wdf01000.sys Blue Screen error. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.
  • Open the Command Prompt with admin privileges.
  • Then type in the following commands and make sure to hit Enter right after you type each one of them:
    • Dism /Online /Cleanup-Image /CheckHealth
    • Dism /Online /Cleanup-Image /ScanHealth
    • exe /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 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 – Use the Driver Verifier Manager

The Driver Verifier Manager is another tool in Windows that could help you fix driver-related issues. And so if you want to fix the Wdf01000.sys Blue Screen error, you need to use the Driver Verifier Manager:
  • 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 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 to good system files. 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:
  1. Windows Resource Protection did not find any integrity violations.
  2. Windows Resource Protection found corrupt files and successfully repaired them.
  3. Windows Resource Protection found corrupt files but was unable to fix some of them.
  • Reboot your computer.

Option 5 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like Wdf01000.sys. It can be found on 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.
  • 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.
Read More
Windows Update service could not be stopped
If you are running the Windows Update service but decided to stop it but you encountered an error message instead that says, “The Windows Update service could not be stopped”, read on as this post will help you fix the problem. This kind of error appears when you use the Command Prompt to stop the Windows Update service, especially if you are using cmd without admin privileges. A lot of users reported that they were not able to disable the automatic Windows Update in Windows 10 using Command Prompt. The command used to stop the Windows Update service is the “net stop wuauserv” command. However, when some users executed this command, they got the error message. So if you are one of these users that can’t stop the Windows Update Service via Command Prompt, you can try to fix that using PID as well as checking the Service dependencies. For more details, follow the given options below.

Option 1 – Try to stop the Windows Update service via PID

In case you don’t know, each running service or process has its own unique ID or PID and you can find it in the Task Manager. You can use it to stop the Windows Update service. How? Refer to these steps:
  • Tap the Ctrl + Shift + Esc keys to open the Task Manager.
  • Next, go to the Services tab and look for the service named “wuauserv” and get its PID.
  • After that, type “cmd” in the Windows Start search 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: taskkill /f /pid <PID>
Note: You need to replace “<PID>” with the PID of the “wuauserv” service. For instance, the PID is 6676, then this is how the command should be “taskkill /f /pid 6676”.
  • After you execute the command, you will this message on your screen, “SUCCESS: The process with PID 6676 has been terminated” which indicates that you have stopped the Windows Update service successfully.

Option 2 – Try to check the Service dependencies

Dependencies of a Windows Service in Windows 10 are when windows services depend on other services. Such is the case with the Windows Update service – it also depends on three different services such as the Remote Procedure Call or RPC service, DCOM Server Process Launcher, and the RPC Endpoint Mapper. Meaning to say, if two of these services are not working as expected, then the dependant service will also be affected. This could be the reason why the Windows Update service could not start.
  • Tap the Win + R keys to open the Run dialog box.
  • Next, type “services.msc” in the field and hit Enter to open Windows Services.
  • From the list of Services, look for the following services:
    • Remote Procedure Call (RPC) Service
    • DCOM Server Process Launcher
    • RPC Endpoint Mapper
  • After you find these services, double click on each one of them and check whether the Startup type for all is set to Automatic and the Service status is set to Running or not.
  • If the service status is not running, then click the Start button. Afterward, check if you can now run the Windows Update service.
Read More
Fix Error 0xe0434f4d

What is Error 0xe0434f4d?

Error 0xe0434f4d displays when a remote computer runs an instance of the SQL Server 2005 but it fails to initialize. When the plan is started, this error displays in a status window on the SQL Server. Also, when the Update-OffilineAddressBook cmdlet is started in Microsoft Exchange Server, this error can occur.

Solution

Restoro box imageError Causes

Error 0xe0434f4d can occur for possibly two main reasons. The first one is when the System Attendant Service is not properly running, and the second when you don’t have the permission to run the update. Other causes are when the .NET Framework 2.0 security does not allow sqlplanlaunch access to run from a shared network. Another cause is when the Offline Address Book (OAB) is not found in the Configuration Domain Controller server that the server of OAB generation uses.

Further Information and Manual Repair

In case you didn’t know, the Offline Address Book generation server is a mailbox server, and in order to resolve error 0xe0434f4d, you will have to replicate the OAB object to the Configuration Domain Controller server. In order to do so, follow steps:
  • Go to start and click on All Programs, then go and click on Microsoft Exchange Server 2010. Click on Exchange Management Console
  • In Exchange Management Console, go to Server Configuration and click on Mailbox
  • In the details, go to mailbox server that generates Offline Address Book and right-click it, then go to Properties
  • In the Properties, click on System Setting and locate the domain controller name in the box that reads Domain controller servers being used by Exchange
Make sure the OAB object is reproduced in the Configuration Domain Controller Server. Follow these steps to do that:
  • Go to Start and click on Run. Type Adsiedit.msc in Open box and press Enter. Right-click on ADSI Edit and click on Connect to
  • Locate a list reading Select a well-known naming context, and from there select Default naming context. In a Select or type a domain or server window, type FQDN (fully qualified domain name) of the Configuration Domain Controller server which was determined in step 1, and click OK
  • Expand Configuration [dc.domain.com], expand CN=Configuration, DC=domain, DC=com, expand CN=Services, expand CN=First Organization, and expand CN=Address Lists Container
  • Click on CN=Offline Address Lists and make sure the OAB object is listed on the details pane
When the OAB generation server receives this, then it will connect to the Configuration Domain Controller server and will locate the OAB object. If the OAB generation server is unable to find the OAB object, then the error will return on the cmdlet. On SQL Server, you should change the .NET permissions to allow sqlplanlaunch application access to run from shared administration. For that, follow these steps:
  • On ArchiveIQ Server, open System from the Control Panel and note down the computer name
  • On SQL Server, log in as administrator and open the command prompt
  • On the command prompt type, ‘C:windowsmicrosoft.netframeworkv2.0.50727caspol.ece –m –ag l – url file:\[Archive IQServer Computer Name]AlQRemote$*FullTrust and Press Enter. Type yes and press Enter again to confirm the permission changes.
Read More
1 2 3 171
Logo
Copyright © 2023, ErrorTools. All Rights Reserved
Trademark: Microsoft Windows logos are registered trademarks of Microsoft. Disclaimer: ErrorTools.com is not affiliated with Microsoft, nor claims direct affiliation.
The information on this page is provided for information purposes only.
DMCA.com Protection Status