Windows 11 different sounds for dark theme

Microsoft has been bringing new lock-screen features with every iterative feature release of Windows 10 in order to improve user experience. However, Windows 10 users have different opinions regarding it. Some users are pleased with it while some users simply do not like it. So if you are one of the users who seem to not approve of this feature, read on as this post will be about enabling or disabling the Console Mode sign-in feature in Windows 10. Before you proceed, take note that you will not be able to use your mouse pointer in this Consol Mode login screen and you can only use your keyboard to navigate around various options. You might also want to create a System Restore point just in case. To enable or disable the Console Mode sign-in in your Windows 10 computer, refer to the given steps below. Step 1: Tap the Win + R keys to open the Run dialog box. Step 2: Then type in “Regedit” in the field and tap Enter to open the Registry Editor. Step 3: Next, navigate to the following registry path:

ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionAuthenticationLogonUITestHooks

Step 4: From there, look for a DWORD named “ConsoleMode”. If you don’t see this DWORD, you can just create a new DWORD and name it as “ConsoleMode” and make sure that its base is set to Hexadecimal. Step 5: After that, double click on ConsoleMode and change its value to “0” to disable it and “1” to enable it. Step 6: Now restart your computer to apply the changes made. Like pointed out, you can only use your keyboard when you’re in the Console Mode login window or screen. You can just use the ESC button to go back to the menu while you can utilize the arrow keys so you can go through the options that are mostly vertically arranged and the Enter key to select an option. In the Console Mode, sign-in using the Passwords and PINs worked efficiently.

If you’re having some problem browsing multiple websites on the Firefox browser on your Windows 10 computer, then this post might be of help. One of the most common problems you could encounter in Firefox is mostly related to HTTPS and one of them is the MOZILLA PKIX ERROR MITM DETECTED or ERROR SELF SIGNED CERT or SEC ERROR UNKNOWN ISSUER error which means that Firefox was unable to trust certificates issued on secured websites. If you encounter the MOZILLA_PKIX_ERROR_MITM_DETECTED error in Firefox, this indicates that something in your network or system is interrupting your connection and injecting certificates and when that happens, Firefox won’t trust it. In such cases, one of the culprits is malware. Malware will try to replace a legitimate certificate with its certificate. Another cause is security software where it keeps a tab on a secure connection and creates a false positive, for instance:

“In Microsoft Windows accounts protected by Family Safety settings, secure connections on popular websites like Google, Facebook and YouTube might be intercepted and their certificates replaced by a certificate issued by Microsoft in order to filter and record search activity.”

And if you are connected to a corporate network, there might be a monitoring/filtering product that could be replacing certificates. Moreover, there are also users who reported getting this issue when they use the Nightly version of Firefox. And if that’s the case, you have to try accessing secure websites using only the stable build especially when it comes to payments. However, if you are not doing that, then here are some options you need to check out.

Option 1 – Try turning off HTTPS Scanning on your security and antivirus programs

Each security-based software has a security option that allows you to turn off the HTTPS scanning functionality. They may be available under different names such as HTTPS Scanning, Scan SSL, Show safe result, Do not scan encrypted connections, etc. Find what is applicable for your security or antivirus software and then try turning it off temporarily and see if it helps in fixing the MOZILLA_PKIX_ERROR_MITM_DETECTED error in Firefox.

Option 2 – Try to disable security.enterprise_roots.enabled

The next thing you can do if the first option didn’t work is to disable security.enterprise_roots.enabled which is an HTTPS certificate check on Firefox. Note that this is not recommended but you have to at least try in order to fix the error.

• Open Firefox and then type “about: config” in the Firefox address bar and hit Enter.
• After that, if an info message appears, confirm it.
• Next, search for the security.enterprise_roots.enabled preference and once you found it, double click on it.
• Then change its value to true and restart the Firefox browser once. This will import all the custom certificates from the other security software into Firefox. As a result, it will make sure to mark those sources as trusted and you won’t get the MOZILLA_PKIX_ERROR_MITM_DETECTED error.

One of the essential parts of the Windows 10 operating system is the Microsoft Store as it is the distribution hub of numerous applications such as Netflix, Facebook, and many more. In fact, Microsoft is planning to make it a hub not just for UWP applications but also Windows Classic applications. Microsoft has already built a bridge with the power of Project Centennial which allows developers to migrate and upload their Windows Classic applications to the Microsoft Store. Although the Microsoft Store has been constantly improving, there are still times when you might face an error while using it. One of these errors is error 0x80131500. When you encounter this error, you will get the following error message on your screen:

“Try that again, Something happened at our end, Waiting a bit might help, The error code is 0x80131500 in case you need it.”

To fix this error, you can try changing your internet connection, toggle the date & time settings, change DNS, create a new user account, run the Microsoft Store Apps troubleshooter or reset the Microsoft Store as well re-register it using Windows PowerShell.

Option 1 – Try changing your internet connection

The first thing you can do is to change your internet connection. If you are using Ethernet, you can try to connect to a Wi-Fi connection instead and see if it helps.

Option 2 – Try to toggle the Date and Time settings

The first thing you can try is to sync the Date and Time of your computer as the wrong Date and Time settings are one of the most common causes of connection problems like the error 0x80131500. This is because of the incompatibility between the SSL Certificate validation date and the System Clock. Thus, you have to sync your System Clock. Refer to the steps below to do so.

• Start by tapping the Win + I keys to open the Windows Settings.
• Next, go to Time & Language > Date & time.
• From there, turn the toggle on for the “Set time automatically and Set time zone automatically” option on the right-side panel.
• After that, click on Region & language located on the left side panel and make sure that the Country or region on the right-side panel is set to the country you live in.
• Now close the Settings app and restart your computer and see if it fixes the problem or not.

Option 3 – Try to change the DNS Server

In this option, you can try changing your current DNS settings to the Google Public DNS as it could also help in fixing error 0x80131500. To do so, follow the steps below.

• The first thing you have to do is right-click on the network icon in the Taskbar and select Network and Sharing Center.
• Next, click on the “Change Adapter Settings” option.
• After that, search for the network connection that you are using to connect to the internet. Note that the option might be “Wireless Connection” or “Local Area Connection”.
• Right-click on your network connection and click on Properties.
• Then select the new window to choose the “Internet Protocol 4 (TCP/IPv4)” option.
• After that, click on the Properties button and click the checkbox in the new window for the option “Use the following DNS server addresses”.
• Type in “8.8.8.8” and “8.8.4.4” and click OK and exit.

Option 4 – Try to create a new Administrator User account

If you have a standard account, you can try creating a new account but this time, you create an administrator user account and then see if the error is fixed or not. Note that you have to sign in with your main account before you can create an admin account.

Option 5 – Run the Microsoft Store Apps troubleshooter

The Microsoft Store Apps Troubleshooter will help you in fixing the error 0x80131500. This is a great built-in tool from Microsoft that helps users fix any app installation issues. So this is worth a try to solve the problem. This built-in tool also helps you fix the Windows 10 Store if it isn’t working. To use the Windows Store Troubleshooter, follow the steps below.

1. Tap Win + I keys again to open the Windows Settings panel.
2. Go to Update & Security and then go to Troubleshoot.
3. On your right-hand side, scroll down to find the Windows Store Apps and then click on the Run the troubleshooter option and see if it fixes the problem.

Option 6 – Try to reset the Microsoft Store cache

Just like browsers, Microsoft Store also caches as you view apps and games so it is most likely that the cache is no longer valid and must be removed. To do so, follow the steps below.

• Right-click on the start button and click on Command Prompt (administrator).
• Next, type in the command, “exe” and tap Enter. Once you do, the command will clear the cache for the Windows Store app.
• Now restart your PC and afterward, try opening Microsoft Store again and then try to install your app or update your computer again.

Option 7 – Try to re-register the Microsoft Store app via PowerShell

• Tap the Win + X key combination or right-click on the Start button and click on the Windows PowerShell (Admin) option.
• If a User Account Control or UAC prompt appears, just click on Yes to proceed and open the Windows PowerShell window.
• Next, type in or copy-paste the following command to re-register the Microsoft Store app and tap Enter:

powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRootWinStoreAppxManifest.xml

• Wait for the process to be completed and then restart your computer.

Error Code 0x80240017 – What is it?

Error code 0x80240017 is associated with installing or updating a Windows Store app. This error is more common in Windows 8 and Windows 8.1. It appears due to missing certain system files and also corrupt registry.

Common symptoms

• When you try to install a Windows Store app on a PC running Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2, the installation fails and you receive an error message: 0x80240017
• Certain apps may become unresponsive.
• You may not be able to download apps or Windows update
• You may have difficulty updating or installing and uninstalling other built-in programs inside Windows 8 and Windows 8.1.
• When you have multiple applications running, you may experience crashes and freezes.

Solution

Error Causes

The error code 0x80240017 in Windows 8.1 or Windows 8 usually appears due to the fact that your system has changed after you installed a third-party application. It might also appear if registry entry has changed after a reboot of the operating system and you do not have the required permissions. Other causes may be due to:

• Corrupted, broken, or missing system files.
• Malware/spyware infection or virus attack
• Hardware/RAM decline
• Fragmented file
• Unnecessary or redundant program installations

Further Information and Manual Repair

Repairing Error Code 0x80240017 in Windows 8/Windows 8.1

Method 1:

Resetting Windows Store app:

1. Press and hold the Windows key and press R. This will open up the Run command
2. Now, type exe and hit Enter
3. Just wait for it to finish and it will re-launch Windows Store. Now, try and install the app you were trying to install which was previously showing an error.

This basic solution will delete the cache and reset Windows Store.

Method 2:

Using Windows troubleshooter:

1. Click on Search on the Charm bar and type Troubleshooting. Click on the very first option.
2. A new window will open. Click View all from the left pane.
3. Scroll down to the bottom and click on Windows update.
4. Troubleshooter window for Windows update will pop up. Click on NEXT. It may ask you for administrative permission.
5. The troubleshooter will automatically detect problems and fix them.
6. Now, close this window and try download/install the app which was previously showing an error.

Method 3:

Disable Proxy Settings: Disable proxy server on Internet Explorer

1. Press the Windows + R Run window will appear.
2. Type cpl and hit Enter
3. Click the Connections tab and click LAN settings
4. Under proxy server uncheck “Use a proxy server for your LAN”
5. Click OK

Now try to install apps from Windows Store.

Method 4:

Boot in Safe Mode:

1. Open Run command as previously described
2. Type MSConfig
3. Click on the Boot tab
4. Tick Safe boot in Boot option
5. Select Network
6. Click Apply and OK
7. Reboot your system

Your system will boot in Safe mode with Networking. You may now try and open Windows Store and should not see any errors.

Method 5:

Note: It is recommended that you back up your files and folders before attempting this step:

1. Move the mouse cursor over to the upper right side of the screen.
2. A menu will pop up on the left. Click on the “Settings” feature on the menu.
3. On the Settings window, click on the “Change PC settings.”
4. Now, left-click on the “Update and recovery” feature.
5. For the next step, left-click on the “Recovery” feature.
6. There is an option here saying “Refresh your PC without affecting your files.” There, left-click on the “Get started” button.
7. Now, follow the instructions on the screen to finish the Refresh process.
8. After the Refresh process has finished restart your Windows 8.1 or Windows 8 device.
9. Check again to see if the error 0x80240017 has been fixed.

If you do not possess the technical expertise required to accomplish this yourself or do not feel comfortable doing so, download and install a powerful automated tool to get the job done.

The dxgmms2.sys file is a system driver file in Windows that is associated with the Graphics Rendering capabilities of a computer. However, this file is known to cause various Blue Screen of Death errors. Some of the culprits for these errors include issues with RAM, hard disk issues, corrupted drivers, and incompatible firmware. Despite its many causes, fixing this issue is quite straightforward so it should be easier for you to fix it. Here are some of the Blue Screen errors related to the dxgmms2.sys file:

• SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
• SYSTEM_SERVICE_EXCEPTION
• KMODE EXCEPTION NOT HANDLED
• PAGE FAULT IN A NONPAGED AREA
• IRQL NOT LESS OR EQUAL

If you have recently created a System Restore point prior to getting the dxgmms2.sys Blue Screen error, then you need to perform System Restore first before you further troubleshoot the problem as it might help in resolving the Blue Screen error. Refer to the steps below to perform System Restore.

• First, press 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.

If System Restore didn’t help in fixing the Blue Screen error, now’s the time for you to resort to the troubleshooting tips provided below but before you get started, make sure that you create a System Restore point first.

Option 1 – Reinstall the Graphics Card drivers

• 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 Graphics Card drivers listed under Display Adapters.
• Right-click on each one of the Graphics Card drivers and select Uninstall device and then follow the next on-screen instructions given to uninstall the driver.
• Now reboot your computer. During this time, your system will automatically reinstall the Graphics card drivers.

Note: You also have the option to go directly to the website of your graphics card manufacturer and check if there’s a new update – if there is, download it. After that, you could also check if there’s a new update of the game you’re getting the issue of the black bar.

Option 2 – Try running the DirectX Diagnostic Tool

Since the dxgmms2.sys Stop error has something to do with the DirectX Graphics APIs, you can run the DirectX Diagnostic tool to resolve the problem.

Option 3 – Try updating or re-installing DirectX

If the DirectX Diagnostic tool didn’t work, you can try to update or reinstall DirectX instead. This can help in fixing the problem because when you reinstall or update DirectX, it will replace the incompatible or corrupted components of DirectX from your computer.

Option 4 – Try to update the BIOS

Updating the BIOS can help you fix the Blue Screen error related to the dxgmms2.sys file but as you know, BIOS is a sensitive part of a computer. Even though it is a software component, the functioning of the hardware depends on it largely. Thus, you must be careful when modifying something in the BIOS. So if you don’t know much about it, it’s best if you skip on this option and try the other ones instead. However, if you are well-versed in navigating the BIOS, then follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “msinfo32” in the field and press Enter to open System Information.
• From there, you should find a search field on the bottom where you have to search for the BIOS version and then press Enter.
• After that, you should see the developer and version of the BIOS installed on your PC.
• Go to your manufacturer’s website and then download the latest version of BIOS on your computer.
• If you are using a laptop, make sure that you keep it plugged in until you have updated the BIOS.
• Now double click on the downloaded file and install the new BIOS version on your computer.
• Now restart your computer to apply the changes made.

Option 5 – Use some registry tweaks

• Tap the Win + R keys to launch the Run utility.
• Then type “Regedit” in the field and hit Enter to open the Registry Editor.
• Next, navigate to this registry key: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlGraphicsDrivers
• From there, right-click on the right-side panel and click on New > DWORD (32-bit) Value.
• Then set the name of the new DWORD to “TdrDelay”.
• After that, use the next set of instructions and select the one for the Windows version you are using.

32-bit Windows:

• Choose the DWORD (32-bit) value.
• Then type in “TdrDelay” as the name and hit Enter.
• After that, double click on TdrDelay and add “10” as its value and click OK. This will set the response time for your GPU to be 10 seconds.

64-bit Windows:

• Select the QWORD (64-bit) value.
• Next, type in “TdrDelay” as the name and hit Enter.
• Double click on TdrDelay and type in “10” as its value data and click OK.
• Restart your computer to apply the changes made.

Option 6 – Disable the Sleep Functionality

You might also want to disable the Sleep Functionality as it could be the reason why you’re getting the Blue Screen error. There are times when the graphics card’s drivers are being used in the background and if the display goes to sleep and is awakened, it may cause a Blue Screen error. To fix it, you can prevent your computer from going into Sleep mode.

Option 7 – Try to run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that might help you fix any Blue Screen errors related to the dxgmms2.sys file. 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.
• 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.

If you are trying to install or update Microsoft Edge on your Windows 10 computer but ended up getting HTTP Error 500 or Error 0x8004xxxx or 0x8007xxxx, then you’ve come to the right place as this post will help you sort this problem out. The aforementioned errors when either installing or updating the Edge browser occur due to a Network issue. There is actually a range of error codes that are associated with the network connection issue. These error codes include Error 500 or 0x80010108, 0x80040801, 0x80042193, 0x80042194, 0x800421F4, 0x800421F6, 0x800421F7, 0x800421F8, 0x80072742, 0x80072EE2, 0x80072EE7, 0x80072EFD, and 0x80072EFE. To fix them, there are several options you can try. You can try to run the Network Adapter troubleshooter or update or reset the Network Adapter as well as check and the proxy configuration.

Option 1- Try updating the Network Adapter Driver

Follow the steps below to update your Network Adapter Driver:

• Tap the Win + R keys to launch the Run window and then type in the “MSC” command and hit Enter to open the Device Manager window.
• From there, expand the list of all the network drives and update each one of them.

Note: If updating the network drivers didn’t help in fixing the problem, you can also try to uninstall the very same drivers and restart your Windows 10 PC. After that, the system itself will reinstall the drivers you just uninstalled. Alternatively, you can also download and install the drivers from the manufacturer’s website directly.

Option 2 – 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 3 – Try to reset the Network Adapter

You can also try to perform a Network Reset to resolve the problem. This will reset the entire network configuration including your IP address. To perform Network Reset, follow these steps:

• Tap the Win + I keys to open Settings.
• From there, go to the Network and Internet section.
• Next, scroll down and look for “Network Reset” under the status pane.
• After that, click on Network Reset and then on Reset now to start resetting the network configuration. Once done, check if it is able to fix the error or not.

Option 4 – Try to fix the Proxy Settings

• In the Cortana search box, search for Internet Explorer and then click on the related search result.
• After that, tap the Win + T keys on your keyboard and click on Internet Options.
• Next, navigate to the Connections tab and click on LAN Settings.
• Then click on the Advanced button and delete all the entries in the list generated in the Exceptions section. And if the Advanced button is disabled because the “Use a proxy server for your LAN (These settings will not apply to dial-up or VPN connections)” option is disabled then you are good to go. Now proceed to the next step.
• Tap the Win + X keys or right-click on the Start button and select Command Prompt (Admin) or you could also search for “cmd” in the Cortana search box and right-click on Command Prompt from the search results and select the “Run as administrator” option.
• If a User Account Control appears, click on Yes to proceed. After that, type each one of the commands listed below, and don’t forget to hit Enter after you type each one of them.
  • netsh winhttp reset proxy
  • net stop wuauserv
  • net start wuauserv

• Now restart your computer and check if the problem is fixed or not by installing or updating Microsoft Edge again.

Socket Error 10013 - What is it?

Socket error 10013 is an error code that often pops on the screen when you try to access the server. This error code restricts your permission to access. It shows that your permission request was denied. The error message is displayed in the following format:

“Socket.error: [Errno 10013] an attempt was made to access a socket in a way forbidden by its access permissions”

Solution

Error Causes

Narrowing down a particular reason for the cause of socket error 10013 is difficult, typically because this error code can be generated due to several reasons. Here are some of the common reasons for its occurrence on your PC:

• High-security set up- Firewall or an antivirus program
• Too many functions tied to the same driver confuses the socket
• Outdated drivers
• Malware

The good news is that the socket error 10013 is not fatal. However, it is advisable to fix and resolve the issue to avoid inconvenience.

Further Information and Manual Repair

Here are some of the best, quickest and easiest methods to work around the problem and resolve socket error 10013 without any hassle or delay.

Method 1 - Turn off Firewall

Believe it or not, a high level of internet security measures like Firewalls and anti-virus programs are a common cause of socket error 10013. Firewalls are made to protect a computer from harmful connections but sometimes it may also restrict server connections, considering them as a threat to your system security. Due to this, permission access is adamantly denied. To resolve this issue on your PC, the best way to go about is to turn off your Firewall or any other anti-virus programs installed on your system. Once you turn off these programs, try accessing the server again. The majority of the time the issue is resolved by carrying this step. Nonetheless, if the error still persists, try the methods given below.

Method 2 - Check the Permissions section of the Firewall Program

Another way to resolve this is to check the permission section of the Firewall program and check for the server. If the server is not listed, contact the Internet Service Provider (ISP) and ask for help in adding the server to the list.

Method 3 - Update Drivers

The outdated driver may sometimes be the reason for the socket error 10013.  The socket may no longer use the drivers installed on your PC which is why permission to access the server is not granted. When this is the reason, try updating the drivers to resolve. For new drivers, visit the software manufacturers’ website, download, and install.

Method 4 - Scan for Viruses and Malware

Another alternative is to scan for viruses and malware. Sometimes the cause for the error is a viral infection. Therefore, remove them to resolve. The best way is to download Restoro. This is a user-friendly and next-generation PC Fixer embedded with 6 scanners including a powerful anti-virus. It scans your entire PC and removes all types of viruses including malware, adware, spyware, and Trojans in seconds. Click here to download Restoro.

Windows 10 has a Cloud Clipboard feature that allows users to have a list of multiple copied text in place so that they can reuse it. And each time the computer restarts, the Clipboard Data is cleared. However, you can actually do it manually. How? Read on as this post will walk you through how you can turn on or off as well as clear the Clipboard history in Windows 10. This kind of feature is already available in Windows 10 v1903. In the previous versions of Windows, there was no feature to turn off history in the clipboard and users have to use other ways to clear the clipboard history. And now it seems that Microsoft has put an end to this dilemma as it now allows users to clear the clipboard history. To turn on or off or clear the Clipboard history, here are some instructions you need to follow: Step 1: Tap the Win + X keys to open the power menu and select Settings. Step 2: After that, navigate to Settings > System > Clipboard. Step 3: From there, turn off the toggle button under the Clipboard history section. This will turn off the Cloud Clipboard feature. As a result, the default clipboard will hold one last item and will not display the data on the clipboard. Note: When you tap the Win + V keys to invoke the clipboard manager, you will see a prompt that says, “Can’t show history, See all copied items in place, Turn on clipboard history”. You have the option to turn it back on by simply clicking on the available button. Doing so would only hide the existing data and makes sure that no copy of the data is kept.

Conclusion

On the other hand, if you want to clear the clipboard without affecting its history data, you have to make sure to pin the items on the clipboard that you want to stay. After that, click on the three-dotted icon for the menu and click on the “clear all” option. This will delete all the entries but will keep the pinned items on your clipboard.

Each time you execute a command on your computer, it takes into account a number of files and space for the code in the background for the command to be executed. Thus, executing the command is not that easy which is why you could encounter some errors along the way due to various limitations or poor allocation of memory, and so on. One of the errors you might encounter when executing a command on Windows 10 and Windows Server is the “Not enough storage is available to process this command”. There are several potential fixes you can check out to fix this error. To fix this error, you can try to delete the temporary files in your computer, run the DISM tool or apply some registry tweaks. For more details, refer to each one of the given options below.

Option 1 – Try to delete the temporary files

The error could be caused by some temporary or junk files in your computer and so you need to clear them up to fix the problem. You can achieve that using the Storage Sense feature.

• Open Setting > System > Storage from the WinX Menu.
• From there, you will see a list of all the local and connected storage devices along with the details on the free space. Make sure that Storage Sense is on.
• Next, find a link that says “Free Up Space” and click it to open.
• After that, a screen which is the built-in program in Windows 10 will appear and will scan your computer for the following junk files so you can free up disk space:
  • Windows Upgrade Log Files
  • System created Windows Error Reporting Files
  • Thumbnails
  • Temporary Internet Files
  • Previous Windows Installation Files
  • Delivery Optimisation Files
  • DirectX Shader Cache
• Choose the files you want to get rid of and then click on the remove files option. Note that you’ll have an idea of the total size as you select any of the junk files listed above.
• Now go to the “Free Up Space Now” section and click the Clean now button. This will get rid of all the temporary or junk files in your computer and should hopefully fix Error 1310.

Option 2 – Run the DISM tool

You can also run the DISM Tool as it could also help in fixing the “Not enough storage is available to process this command” error in Windows 10. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth” that could help in fixing error 0x80246019.

• You can run the DISM tool via Advanced Startup Options or you could boot your computer into a Clean Boot State and then select Command Prompt.
• 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. Once it’s done, restart your computer and try again. If it didn’t work, you can try to use the “/StartComponentCleanup” parameter: Dism /Online /Cleanup-Image /StartComponentCleanup

Option 3 – Try to use the Registry Editor

The memory range allocated for the tasks and commands to be executed is associated with the IRPStackSize DWORD. Thus, to fix the error, you need to extend the range by applying some registry tweak. Before you proceed, make sure that you create a System Restore point first. Once you’re done, follow these steps:

• Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and tap Enter to open the Registry Editor.
• Next, navigate to this registry key: ComputerHKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesLanmanServerParameters
• From there, look for the DWORD named “IRPStackSize” and right-click on it. If you can’t find this DWORD, just right-click on any empty space and select New > DWORD (32-bit) Value.
• Input “IRPStackSize” as the DWORD name and double click on it and set its Value data to be greater than its default value. Note that the maximum value allowed is “0xc” and the range starts from “0x1”.
• Now click on OK and exit the Registry Editor and then restart your computer and see if the error is fixed.

In previous versions of Windows changing the system, the font was a pretty straightforward process, but it seems Microsoft did not want this feature to keep for whatever reason and there is no option as of the time of the writing of this article to do it in standard options in Windows 10. But do not worry, you are still able to customize your Windows and choose which font would you like to see inside it in all of its dialogs. You can choose whichever font you desire, the only prerequisite is it to be installed on your system. This guide will require you to change values in the registry of Windows itself so please follow step-by-step instructions and always make a backup of the registry before changing it in order to prevent some permanent Windows issues. All of that being said, let's start.

Setting new font

First thing is to open notepad, in the notepad paste the next block of code:

Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts] "Segoe UI (TrueType)"="" "Segoe UI Bold (TrueType)"="" "Segoe UI Bold Italic (TrueType)"="" "Segoe UI Italic (TrueType)"="" "Segoe UI Light (TrueType)"="" "Segoe UI Semibold (TrueType)"="" "Segoe UI Symbol (TrueType)"="" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes] "Segoe UI"="NEW_FONT"

Where in "Segoe UI"="NEW_FONT" instead of NEW_FONT you need to write the exact name of the font that you wish to use as a system font. Once you have replaced the default system font with your desired one, go to File and save as, from file type drop-down menu, choose all files and save this file as .REG type giving it whatever name you wish. When the file is saved, close notepad, right-click on the saved file and choose the merge option. Confirm with YES and click on OK. Reboot your system and your Windows will now use the font of your choice as its default system font.

Restoring default font

If you wish to return the old default system font as it was, follow the same steps but in your notepad paste this code:

Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts] "Segoe UI (TrueType)"="segoeui.ttf" "Segoe UI Black (TrueType)"="seguibl.ttf" "Segoe UI Black Italic (TrueType)"="seguibli.ttf" "Segoe UI Bold (TrueType)"="segoeuib.ttf" "Segoe UI Bold Italic (TrueType)"="segoeuiz.ttf" "Segoe UI Emoji (TrueType)"="seguiemj.ttf" "Segoe UI Historic (TrueType)"="seguihis.ttf" "Segoe UI Italic (TrueType)"="segoeuii.ttf" "Segoe UI Light (TrueType)"="segoeuil.ttf" "Segoe UI Light Italic (TrueType)"="seguili.ttf" "Segoe UI Semibold (TrueType)"="seguisb.ttf" "Segoe UI Semibold Italic (TrueType)"="seguisbi.ttf" "Segoe UI Semilight (TrueType)"="segoeuisl.ttf" "Segoe UI Semilight Italic (TrueType)"="seguisli.ttf" "Segoe UI Symbol (TrueType)"="seguisym.ttf" "Segoe MDL2 Assets (TrueType)"="segmdl2.ttf" "Segoe Print (TrueType)"="segoepr.ttf" "Segoe Print Bold (TrueType)"="segoeprb.ttf" "Segoe Script (TrueType)"="segoesc.ttf" "Segoe Script Bold (TrueType)"="segoescb.ttf" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes] "Segoe UI"=-

Reboot your system and your Windows will now revert the font of your choice as its default system font.