Logo

Make START menu full screen in Windows 10

Hello and welcome to another great tutorial from errortools.com. Today we will be making Windows START menu full screen.

First introduced in Windows 8.1, the start menu has been shifted from full screen to gadget like in Windows 10 but if you prefer to have it over the entire screen with all of its glory and large icons you can do so and we will be happy to show you how.

Press ⊞ WINDOWS and choose settings.

Windows 10 Star menu with marked settings iconFrom the settings screen, choose Personalization.

Windows 10 settings menu with marked Personalization groupUnder personalization options click on START.

windows settings start screen sectionAnd then on the right part click on the button under Use Start full screen to turn it ON

windows settings start screen switch for full screenThat's it, your start menu is now full screen.

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

How to get Dynamic Wallpapers in Windows 10
Dynamic Wallpapers introduced with Mojave Update in macOS are pretty cool. Dynamic Desktop is a feature introduced in macOS Mojave (10.14), in which the desktop background changes according to the time of Mac's current location. If Location Services are turned off the Privacy pane of the System Preferences, then the time zone specified in the Date & Time preferences will be used. To apply macOS Dynamic Wallpaper on Windows 10 we need to download & use WinDynamicDesktop, a free application that lets you apply macOS Dynamic Wallpaper. After the installation, you will be asked to Configure the Schedule. While doing that you need to make sure that you enter your location correctly. You can even set specific sunrise and sunset timing by selecting “Use specific sunrise and sunset times” and changing the Sunrise and Sunset times manually. Now, you will be greeted with some of the coolest dynamic wallpapers in the market. Select a theme of your choice, click on the Download button (file size can range between 20-200 MB), and click Apply to enjoy macOS Dynamic Wallpaper on Windows 10. If for some reason you want to go back to the default Windows theme but not necessarily delete the application then right-click on the WinDynamicWallpaper icon from the taskbar, click Select Theme, select None (from the theme section) and click Apply.
Read More
Fix BAD_SYSTEM_CONFIG_INFO error in Windows
If you encounter the BAD_SYSTEM_CONFIG_INFO Blue Screen error in your Windows 10 PC, then read on as this post will guide you in fixing this issue. Usually, this kind of Blue Screen error is caused by some issues with the Boot Configuration Data file. The main issue inside of the Boot Configuration Data file is that either some boot order files or older files might be in conflict with the newer ones or the stable ones and thus triggering the BAD SYSTEM CONFIG INFO Blue Screen error. This kind of Stop error also indicates that there is an error in the Windows Registry which is why you need to update potential culprit drivers as well as edit some entries in the Registry if need be. But before you get started, make sure that you create a System Restore Point first. After creating a System Restore Point, try to boot your computer into Safe Mode and then restart your computer normally. However, if it doesn’t work, proceed to the given options below.

Option 1 – Run System Restore

Performing System Restore might help you in fixing the BAD SYSTEM CONFIG INFO Blue Screen error. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.
  • Tap the Win + R keys to open the Run dialog box.
  • After that, type in “sysdm.cpl” in the field and tap Enter.
  • Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
  • After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

Option 2 – 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 – Try fixing the Windows Registry files

In order to fix the Windows Registry files, you need to make a bootable Windows 10 USB drive and then boot your PC using it. To do so, refer to the steps below.
  • Once you see the Welcome Screen, click on Next.
  • Then click on the “Repair your computer” option located on the bottom-left section of the window.
  • Next, click on Troubleshoot > Advanced Options > Command Prompt.
  • After opening Command Prompt, execute each one of the commands listed below in the sequence that they are given:
    • CD C:WindowsSystem32config
    • ren C:WindowsSystem32configDEFAULT DEFAULT.old
    • ren C:WindowsSystem32configSAM SAM.old
    • ren C:WindowsSystem32configSECURITY SECURITY.old
    • ren C:WindowsSystem32configSOFTWARE SOFTWARE.old
    • ren C:WindowsSystem32configSYSTEM SYSTEM.old
  • After executing the commands given above, type in the next ones below and make sure to execute them in the given sequence below.
    • copy C:WindowsSystem32configRegBackDEFAULT C:WindowsSystem32config
    • copy C:WindowsSystem32configRegBackSAM C:WindowsSystem32config
    • copy C:WindowsSystem32configRegBackSECURITY C:WindowsSystem32config
    • copy C:WindowsSystem32configRegBackSYSTEM C:WindowsSystem32config
    • copy C:WindowsSystem32configRegBackSOFTWARE C:WindowsSystem32config
  • Now type “exit” to close Command Prompt.
  • Restart your PC for the changes to take effect.

Option 4 – Run a Memory Check to test RAM

On the other hand, you can also fix the BAD SYSTEM CONFIG INFO Blue Screen error by running a Memory Check using the Windows Memory Diagnostic. Refer to these steps to do so.
  • Tap the Win + R keys to open the Run dialog box.
  • Then type “mdsched.exe” in the field and hit Enter to open the Windows Memory Diagnostic.
  • After that, the Windows Memory Diagnostic will give out two options such as:
  1. Restart now and check for problems (recommended)
  2. Check for problems the next time I start my computer
  • Select any of the given options. After that, your computer will restart and check for memory-based issues upon the restart. If there are any issues, it will automatically them.

Option 5 – Rebuild BCD files and repair MBR files

Like what you did on the third option above, you also have to make a bootable Windows 10 USB drive for this option and then boot your Windows 10 PC using it.
  • Once you get to the Welcome Screen part, click on Next.
  • Afterward, click on the Repair your computer option located on the bottom-left part of the window.
  • Then click on Troubleshoot.
  • Next, select the Advanced Options and then Command Prompt.
  • Once Command Prompt has been pulled up, enter each one of the following commands and in the sequence that they are given to rebuild BCD files and repair MBR files:
    • bootrec /repairbcd
    • bootrec /osscan
    • bootrec /repairmbr
  • Now type “exit” to close Command Prompt and then restart your computer to successfully apply the changes made.
Read More
Fix KMODE EXCEPTION NOT HANDLED e1d65x64.sys
KMODE_EXCEPTION_NOT_HANDLED seems to be connected primarily to a third-party driver, e1d65x64.sys associated with the Intel(R) Gigabit adapter, NIC/Wired network NDIS (Network Driver Interface Specification) 6.x driver. Error is known to produce the dreaded blue screen of death or BSOD. Most usually error is connected with gaming on Windows 10 computer and it manifests itself during gaming sessions. If you are unlucky and you are faced with this unfortunate error we will be happy to try to help you and present with tips and tricks in order for you to find a solution for it. Before you proceed with the provided solutions, be sure you have sufficient disk space on the Windows drive, run Disk Cleanup and then run CHKDSK.

1) Run the Blue Screen Online Troubleshooter

Open Control Panel, change the view setting to icons. Click Troubleshooting, and click “View all” in the tasks pane. Click “Blue Screen”. This opens the Blue Screen Troubleshooter.

2) Run Driver Verifier

  1. Start a Command Prompt window by selecting Run as an administrator, and type verifier to open Driver Verifier Manager.
  2. Select Create standard settings (the default task), and select Next. You can also choose to Create custom settings to select from predefined settings, or to select individual options. For more information, see Driver Verifier options and rule classes and Selecting Driver Verifier Options.
  3. Under Select what drivers to verify, choose one of the selection schemes described in the following table.
    Driver verifier table:
    Option Recommended use
    Automatically select unsigned drivers Useful for testing on computers that are running versions of Windows that do not require signed drivers.
    Automatically select drivers built for older versions of Windows Useful for testing driver compatibility with newer versions of Windows.
    Automatically select all drivers installed on this computer Provides maximum coverage in terms of the number of drivers that are tested on a system. This option is useful for test scenarios where a driver can interact with other devices or drivers on a system. This option can also exhaust the resources available for Special Pool and some resource tracking. Testing all drivers can also adversely affect system performance.
    Select driver names from a list In most cases, you will want to specify which drivers to test. Selecting all drivers in a device stack allows the Enhanced I/O Verification option to track objects and check compliance because an I/O request packet (IRP) is passed between each of the drivers in the stack, which allows for a greater level of detail to be provided when an error is detected. Select a single driver if you are running a test scenario that measures system or driver performance metrics, or if you want to allocate the greatest number of resources available for detecting memory corruption or resource tracking issues (such as deadlocks or mutexes). The Special Pool and I/O Verification options are more effective when used on one driver at a time.
  4. If you chose Select driver names from a list, select Next, and then select one or more specific drivers.
  5. Select Finish, and then restart the computer.

3) Update network device drivers

Go to the official Intel website and try to find newer versions of drivers, if there are none perhaps you will need to revert back to the previous version.

4) Scan memory for issues

Run a memory test on your system, sometimes these errors can be traced back to a faulty RAM bank.

5) Stop over-clocking your PC

If you have overclocked your PC please reverse it back to its original state and see if that would solve the issue

6) Perform System Restore to the previous restore point

If none of the previous solutions have bared fruit, roll back to a previous restore point and that should solve the issue.
Read More
3 ways to bypass TPM and install W11 anywhere
TPM 2.0 requirement for Windows 11 has produced a lot of discussions since it was announced. A lot of somewhat older hardware seems to be left behind with this decision from Microsoft. So naturally, when something like this is announced, especially when it is stated it is the must-have thing, people find a way to break it and to prove it is not the case. In that spirit, I am proud to present you with not one but three-way you can install Windows 11 on hardware that does not has TPM 2.0. Please note that by bypassing this you will not be able to use some Windows 11 features tied to modules like Device encryption, vTPM in Hyper-V, and all TPM-related services. I will cover methods from the most simple and straightforward ones to the more complicated using registry editor.

Windows 11 TPM installationBypass TPM with changing installation media

For this method to work you will need both Windows 10 ISO and Windows 11 ISO since it will require some file copying between them. You will also need Rufus or another tool to make a new installation media once files are copied All you have to do in this method is to go into your Windows 10 ISO and delete the install.esd, then just copy install.wim from Windows 11 installation media into the same place, and you are done. Make install ISO with Rufus and install Windows 11.

Change DLL on installation media method

For this method, you will need everything like in the previous one and the process is almost the same, but this time instead of migrating the whole installation file, we will just replace the appraiserres.dll file. Copy appraiserres.dll file from your Windows 10 installation media over the same file on Windows 11 installation and you are good to go.

Bypassing TPM via registry editor

If for some reason previous easy solutions have not worked for you do not lose hope just yet, there is one more way you can bypass TPM. In this given method you will not need Windows 10 installation media but the process is a little more complicated than previous ones.
  1. Create Windows 11 media installation
  2. Start the installation process
  3. Click the Next button.
  4. Select region, language, and time when asked. You can change these settings later.
  5. Click the Install now button.
  6. If your device was already activated, click the I don’t have a product key option to continue.
  7. Click the Next button. Select the edition of Windows. When you’re installing the OS on an existing device, Windows won’t activate if you select the incorrect edition.
  8. Click the Next button.
  9. Select the I accept the license terms option and click next.
  10. Select Custom: Install Windows only (Advanced)
  11. During the Windows installation screen, now you will see a message stating that the PC can’t run Windows 11 if you do not have TPM 2.0
  12. On this screen, press SHIFT + F10 to open Command Prompt window.
  13. Launch the registry editor, type regedit.exe in Command Prompt, and press ENTER
  14. Create a new key “LabConfig” by right-clicking on the Setup key and select New > Key under HKEY_LOCAL_MACHINE\SYSTEM\Setup.
  15. Type LabConfig and press ENTER.
  16. Right-click on the LabConfig key.
  17. Select New > DWORD (32-bit) value.
  18. Create two values: BypassTPMCheck and BypassSecureBootCheck.
  19. Set their DWORD32 value to 1.
  20. Press ENTER.
  21. Close the Registry Editor.
  22. Type exit in the Command Prompt and press ENTER or close its window.
  23. Press the back button in the Windows installation setup if it still says “This PC can’t run Windows 11”.
  24. Accept the terms & conditions.
  25. Select Custom: Install Windows only (Advanced) option and configure the partition with the current installation.
  26. Click the Next button.
  27. Finish Windows 11 installation
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
MS releases ISO for Windows 10 build 21354
On April 7th Microsoft has released Windows build 21354 for their flagship OS and updates are rolling. Alongside the new update builds Microsoft has decided to create and release Windows 21354 build as an installable ISO image for anyone who wishes to do a clean installation of Windows without the need to update it after the installation. We have not seen this move by Microsoft in a long time and honestly, we are welcoming it, it is always great to have updated ISO Windows build than to install the old version and sit through an hour or more of updates. If you are interested in getting this ISO image and you are part of the insider program you can download it from here. If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.
Read More
4 Methods of Fixing Error Code 48

Error Code 48 – What is it?

Error Code 48 is a device driver error code that users can encounter on any Windows 2000 operating system and later versions.

It occurs when the connected peripheral device cannot be run as the Windows operating system’s driver required to install the programs for peripheral devices has either been corrupted or is incompatible with the system.

It prompts the user with the following message on the screen:

The software for this device has been blocked from starting because it is known to have problems with Windows. Contact the hardware vendor for a new driver. (Code 48)

Solution

driverfix boxError Causes

Like most other Windows error codes, error code 48 is triggered by the following factors.

  • Corrupted system registry files
  • Presence of viruses in the device
  • The device driver is out-of-date
If this error code is not rectified, it could give birth to other driver device errors such as error code 52.

Further Information and Manual Repair

Method 1 – Run a complete scan for malware and spyware

Identifying and removing the viruses in the system registry and in the connected devices is the easiest method to fix the corrupted registry files.

Viruses such as spyware and malware infect the registry entries and eat up the files that lead to incomplete or missing data. This creates problems for installing external devices as the driver required to install them is not complete.

Method 2 – Use System Restore

You can also use system restore to eliminate the problem. Here is how you can use it:

  • 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 to 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 the last saved system checkpoint, you can obtain undamaged Windows system registry files that can help resolve the error code.

Method 3 – Manually uninstall and reinstall the device driver

Since Error Code 48 is due to a missing or an out-of-date device driver, uninstalling and then reinstalling the device driver can help solve the error.

You can do this by firstly logging in as Administrator and opening Device Manager. Select the device that is causing the problem and double click it; 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 48. It also has the added advantage of being able to backup and restores 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 48 quickly and effectively!
Read More
Attempt was made to reference a token
If you were trying to open File Explorer but it suddenly stopped working and you encounter an error message that states, “An attempt was made to reference a token that does not exist”, read on as this post will guide you in fixing this problem. This problem was initially reported after the April Update and Microsoft was able to fix it right after correcting the build. However, this effort seems futile for some users as recently, some reported getting the same error when they try to open not just Windows File Explorer but also with utilities like Microsoft Management Console or MMC, Visual Studio, Task Manager, Printer, Recycle Bin, etc. Two of the most likely causes of this error are a troublesome Windows Update and corrupted system files. Whatever the cause is, here are some suggestions you can follow to fix the “An attempt was made to reference a token that does not exist” error.

Option 1 – Try to re-register the problematic DLL file

You may have to re-register the ntdll.dll file using the regsvr32.exe before you can successfully install the program and fix the ntdll.dll file crash error. The Regsvr32 tool is a command-line utility that can be used to register and unregister OLE controls like DLL and ActiveX (OCX) control in the Windows operating system. Follow the steps below to use it.
  • Open Command Prompt as admin from the WinX menu.
  • Next, type the following commands in the elevated Command Prompt and hit Enter to execute the command. This will re-register the affected DLL file using the Windows operating system tool, regsvr32.exe.
    • exe /[DLL file]
    • exe [DLL file]
Note: Replace “[DLL file]” with the name of the DLL file that was pointed out in the error.
  • After you execute the given commands, you should see a message saying, “DllRegisterServer in vbscript.dll succeeded” if the Regsvr32 tool was able to run successfully. After that, try to install the program again and see if it now works.

Option 2 – Replace the DLL file from a trusted source

  • First, you need to get the new DLL file from another computer with preferably the same file version number.
  • After that, you need to boot your PC into Safe Mode and navigate to the paths listed below and then replace the file using a USB drive or other external storage devices.
    • x86: This PC > C:/Windows/System32
    • x64: This PC > C:/Windows/SysWOW64
  • Next, type “cmd” in the Cortana search box and right-click on Command Prompt, and select “Run as administrator” to open it with administrator privileges.
  • Now type the “regsvr32 ntdll.dll” command and hit Enter.
  • Restart your PC and check if the error is now fixed.

Option 3 – Perform a System File Checker scan

The System File Checker or SFC scan could detect and automatically repair damaged system files that could be causing the “An attempt was made to reference a token that does not exist” error to pop up. SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files. 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 and hit Enter.
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.

Option 4 – Try reverting back to the previous build of Windows

This kind of error might have something to do with a Feature Update so you can try to revert your computer to a previous build of Windows 10 as it could help you fix the problem. In this case, it would better if you refrain from updating your Windows 10 computer until this problem is completely resolved by Microsoft.
Read More
CHKDSK cannot continue in read-only mode
As you know, the CHKDSK utility is proven to be one of the useful tools to fix any issues that concerns file system, storage, and disk. However, as useful as it may be, it is still not immune to issues as you could encounter errors when running it. One of these errors is the “One such error is the CHKDSK cannot continue in read-only mode” error. If you receive such an error message while running CHKDSK, then you’ve come to the right place as this post will help you sort the problem out. It is possible that the drive is read-only or that the Write Protection is enabled. It could also be that the drive is already being used and scanned by a different program or utility. To get rid of this error, there are a couple of suggestions you need to check out. You can try to run the CHKDSK utility from Recovery or run it on Boot. You could also try to disable Write Protection. For more detailed steps, follow the given instructions below.

Option 1 – Try to run the CHKDSK utility from Recovery

The first thing you can do to resolve the error in CHKDSK is to run the CHKDSK utility from Recovery. How? Follow these steps:
  • First, boot into the installation environment for Windows 10 from a Windows installation media.
  • Next, click on the “Repair your computer” option.
  • After that, select Troubleshoot > Advanced options > Command Prompt.
  • After opening Command Prompt, type this command and tap Enter: chkdsk <Partition Letter>: /r /f
  • Wait until the disk error checking process is completed.
  • Once it’s done, exit the Command Prompt window and restart your computer and then see if the error is fixed.

Option 2 – Try running the CHKDSK utility on Boot

On the other hand, you can also try to run the CHKDSK utility on Boot so you can fix the error and recover any damaged segments of the drive.
  • Open an elevated Command Prompt and enter this command: chkdsk /r
  • After that, you will a message that says, “Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts? (Y/N)”
  • Type Y and tap Enter to schedule a CHKDSK scan once your computer reboots next time.

Option 3 – Try to remove the Write Protection from the drive

As mentioned, removing the Write-Protection on the concerned drive could also help you fix the problem and there are two ways to get rid of the write protection – you can either use the Diskpart utility or the Registry Editor. How? Refer to the following steps.

Via Diskpart utility:

  • Open Command Prompt with admin privileges and then type the “diskpart” command and tap Enter to execute it.
  • Next, type “list disk” and tap Enter to get the list of all the Disk connects or all the partitions that are formed on those disks.
  • After that, you need to choose one command depending on the list of commands you entered. Type “select disk #” and tap Enter to select the disk or partition you want to select.
  • Then type “attribute disk clear readonly” and tap Enter to Disable the Write Protection on the selected disk or partition.

Via Registry Editor:

  • Tap the Win + R keys to open the Run utility and type “Regedit” in the field and then tap Enter to open the Registry Editor.
  • Next, navigate to the following registry key:
ComputerHKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlStorageDevicePolicies
  • After that, look for the DWORD named “WriteProtect” and double click on it, and then set its Value Data to “0”.
  • Now restart your computer and see if the problem is now fixed or not.
Read More
Change screenshot location

Each time when you press WINDOWS + PrtScn key on your keyboard a screenshot is taken and saved on your Hard drive, to be more precise, it is saved in a specific folder which is in c:\Users\Your user name\Pictures\Screenshots. Now, this specific location is not anything that's bad but it is a little deep and not so user-friendly for quick access.

screenshot properties

Luckily this default location can be changed into any folder that you like.

Changing location

First thing is to open File Explorer and then navigate to your PC. Once you go to your PC, go to Pictures, and inside right-click on the Screenshots folder. If there is no screenshots folder inside, this means that since Windows was installed no screenshots were taken with WINDOWS + PrtScn key combination. Please note that just by pressing PrtScn you will create a screenshot but you will place it inside the clipboard ready to be pasted somewhere, with WINDOWS + PrtScn you are saving the screenshot directly in a file on your hard drive.

So once you clicked on the Screenshots folder, go to the bottom and click on properties. Inside properties go to the Location tab. In the location, tab clicks on MOVE and browse to your new location where you would like screenshots to be saved. Once you select the folder for screenshots, click on the Select Folder button and confirm with OK. After this, Windows will ask you would you like to move existing screenshots into the chosen folder. Click YES or NO, depending on your preference.

After this easy setup, all of your new screenshots will be placed now inside the chosen folder.

Thank you for reading and I hope to see you tomorrow. Take care.

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