Change default audio output for Narrator

Windows 11 brought with it a simplified right-click menu that has limited options. If you would like to bring the old Windows 10 right-click menu you will have to do some registry tweaking but it is doable. Since this requires registry tweak, please follow given solution step by step

1. Press Start and type RegEdit
2. Click on Registry Editor
3. Inside registry editor find next key: Computer\H_KEY_CURRENT_USER\SOFTWARE\CLASSES\CLSID\
4. Right click in the right part of editor window and select New > Key
5. Type in as a name: {86ca1aa0-34aa-4e8b-a509-50c905bae2a2}
6. Right click on {86ca1aa0-34aa-4e8b-a509-50c905bae2a2} key and select New > Key again to create new key inside this one
7. Name inside key InprocServer32
8. Double click the “(Default)” key in InprocServer32 to open it
9. When the Default key opens close it without making any changes by clicking on OK. This will make its value property Blank instead of value not set
10. Close Registry Editor
11. Restart your PC

Once the system is up if the followed solution is applied you will now have an old school menu once right-click is used.

One of the most useful utilities on a Windows 10 computer is the Windows File Explorer. It is undeniably one of the File Managers out there full of features on all the platforms. However, it is not without its issues and one of the most common ones most users encounter is when you are trying to open a folder or a location on File Explorer and it displays a message saying, “Working on it…” as it tries to load the content of that location or folder. This kind of issue mainly occurs to computers that run on an HDD although that doesn’t mean that it can’t happen to other computers that run an SDD. And so if the File Explorer on your Windows 10 computer keeps getting stuck on the “Working on it…” message along with a green animation bar moving very slowly while loading the contents of the folder, then it’s best if you follow the options given below to resolve this problem.

Option 1 – Try deleting the contents of the Automatic Destinations folder

• Tap the Win + R keys on your keyboard to open the Run utility.
• And then type “%AppData%MicrosoftWindowsRecentAutomaticDestinations” and hit Enter to open this location.
• From there, select all the files and tap the Shift + Delete key combination.
• After that, you will get a prompt that will ask you if you want to delete all the files permanently, just click on Yes. This will delete all the Quick Access cache.
• Now check if you can now open a folder or a location without the “Working on it…” message.

Option 2 – Try to rebuild the Search Index

• First, open the Indexing Options using the Search bar.
• Next, click on the appropriate listing, e.g. Users folder.
• After that, click on the Advanced button. This will open a mini-sized window and from there, go to the Index Settings tab.
• Then click on the “Rebuild” option under the Troubleshooting section.
• Now click on OK after the rebuilding is completed. This should rebuild the search index for all the files and thus, fix the File Explorer stuck on the “Working on it…” message.

Option 3 – Try to optimize the folder for General Items

You might also want to try optimizing the folder for General Items as it can help the File Explorer to load the contents faster.

• Just right click on the folder that takes time to load the contents in it and is showing the “Working on it…” message.
• After that, click on Properties to open the Properties mini window.
• From there, go to the Customize tab and click on the drop-down menu to “Optimize this folder for” under the “What kind of folder do you want?” section and then select General Items.
• Then check the checkbox with a label that says, “Also apply this template to all subfolders” and click on the OK button to save the changes.
• Restart File Explorer and check if the problem is now fixed or not.

Option 4 – Try performing a System Restore

Running System Restore can also help you resolve whatever issue that’s causing the “Working on it…” message. 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.

Stop 0x0000000A - What is it?

Stop 0x000000A is a type of blue screen of death error associated with Windows XP. It occurs either during or after the installation of Windows XP. In other cases, the stop 0x000000A error may occur when the device driver uses an incorrect memory address, causing an IRQ conflict. The Stop 0x000000A error message means that a process or a driver attempted to access a memory section without permission.  The stop error message is displayed in the following format:

Stop: 0x0000000A (parameter1, parameter2, parameter3, parameter4) IRQL_NOT_LESS_OR_EQUAL *** Address x has base at x - filename

Solution

Error Causes

The stop 0x000000A error is triggered due to multiple reasons. These include:

• Faulty hardware
• The poor device driver installation
• Incompatible device driver
• Viruses and malware attack
• Disk fragmentation

Blue screen of death errors like the stop 0x000000A error code is critical. These errors may pose serious PC threats. When this error occurs the computer screen turns blue, the program running on the system stops and if the error is not fixed in time it may also result in a system crash and failure.

Further Information and Manual Repair

To resolve the Stop 0x000000A error on your PC, here are some solutions that you can try:

1. Roll Back Drivers

To do this, click on the start button and go to the control panel. Then double click the system icon and locate the ‘System Properties’ window. After that click on the ‘hardware’ tab and then click the ‘Device Manager’ button. Here locate the device that you recently updated which could be causing the IRQ conflict. Now double click the device recently updated and click the driver tab. Then click on the ‘Roll Back Driver' button. Wait for the process to finish and then simply reboot your system.

2. Specify the Hardware Abstraction Layer (HAL)

Another method to resolve the Stop 0x000000A error on your system is to specify the hardware abstraction layer (HAL). This can be done during Windows XP installation startup. Simply press the F5 button on your keyboard while the “Setup is inspecting your computer’s hardware configuration’. When prompted, make sure that you specify the correct computer type and HAL (the Hardware Abstraction Layer). Most computers use a single processor, if your computer also has a single processor then simply select ‘Standard PC HAL’ computer type from the menu. Now reboot your PC and then reinstall the Windows XP operating system. If the error is still not resolved then try turning off features in CMOS settings

3. Turn off Features in CMOS Settings

Turn off all the following features in the CMOS settings:

• All caching, including L2, BIOS, internal/external, and write back caching on disk controllers
• Plug and Play
• All shadowing
• Any BIOS-based virus protection feature

After turning off these features, try reinstalling Windows XP again. If this works, then that’s great! However, if it doesn’t, then try method 4; maybe the cause of the stop 0x000000A is associated with incompatible drivers.

4. Install Windows XP compatible Drivers

Sometimes device driver compatibility can also shoot up the stop 0x000000A error message. First, remove the drivers that are incompatible with Windows XP. Now obtain and install new Windows XP compatible drivers. To do this, go to the start menu and the control panel. Now double click on Add or Remove Programs icon. Select the drivers that are incompatible with Windows XP and click on the remove button. After that restart PC and install Windows XP, compatible drivers, for the hardware devices on your system.

5. Scan for Viruses and Repair the Registry

If all the methods discussed above do not resolve the stop 0x000000A error on your PC, then it means either your computer is affected by an infection virus or the problem is associated with the registry like disk fragmentation and invalid entries. To scan for both viruses and registry issues simultaneously in seconds, it is advisable to download Restoro. Restoro is an advanced and multi-functional PC repair tool integrated with powerful utilities including a registry cleaner, antivirus, and a system optimizer. It also scans for Active X controls and class ID errors. The registry cleaning utility scans your entire PC for all possible registry issues triggering different error codes including the stop 0x000000A error. It wipes out all the unnecessary files cluttering and damaging the registry including cookies, temporary files, junk files, and invalid entries. It repairs the fragmented disk and the registry thereby resolving the stop 0x000000A error on your system. The privacy error utility functions like an antivirus. It detects all kinds of malicious software on your system including malware, adware, spyware, and viruses. These are removed immediately thus making your PC error-free. Restoro is safe, efficient, and user-friendly. It is compatible with all Windows versions including XP.  It has a sophisticated interface and a neat layout which makes it quite easy to operate and workaround. Click here to download Restoro and repair your PC and resolve the stop 0x000000A error code now!

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

Option 1 – Try installing Microsoft Visual C++ Redistributable

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

Option 2 – Try to install OpenSSL

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

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

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

Option 3 – Try to check Windows Updates

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

Windows Terminal is a new free Microsoft terminal sort of application. When you open either Power Shell or Command Prompt in Windows they will be opened in different windows, and if you want several of each you will have several windows of each on your screen. Windows Terminal fixes this by opening each of the Instances of Command Prompt and Power Shell as separate tabs inside itself making it much easier to manage multiple instances of named applications. You can also run both Power Shell and Command prompt tabs in the same Windows Terminal. Luckily running command prompt and power shell in different tabs is not the only thing you can do. Windows Terminal lets you choose your own theme, it has emoji support, GPU rendering, split panes, and many more customizable options. Windows 11 will have Terminal as the default command-line environment for opening Power Shell or Command prompt, even Windows Subsystem for Linux (WSL)

Setting Windows Terminal as the default application

If I was successful I have managed to show you that Windows Terminal is something that you should use even if you do not or cannot upgrade to Windows 11. You can use it inside Windows 10 also. First thing is to download and install it. You can get Windows Terminal from the official Microsoft website here: Windows Terminal page After download and installation are completed, open the Terminal app and select the down arrow menu, click Settings. Alternatively, you can use CTRL + + shortcut. Inside Settings by default Default Terminal application would be set to Windows Console Host Click on the Default Terminal application to bring a drop-down menu and choose Windows Terminal from the list. Now by default once opened Windows Terminal will use Power Shell as the default profile, however, you can change this by clicking on the drop-down for the default profile where you can choose between Command Prompt, Power Shell, Windows Power Shell, or Azure Cloud Shell. Pick one that you prefer, click on Save and it will be opened as default on the next run.

If you suddenly find your Windows 10 computer stuck on the “Preparing to configure” screen for quite a long time now after you run Windows Update, read on as you will be guided on how you can fix that issue in this post. During an update process, there’s a lot of things that go on in the background which is why Windows Updates take quite a while before it finishes. It can be at 25%, 50%, or even 100% but the only message you’re going to see on your screen is the “Preparing to configure Windows, Don’t turn off your computer”. However, if you notice that the Windows Update is taking a longer time than it’s supposed to, the first option is to wait some more but if it’s still the same, then there’s definitely something wrong. This kind of issue occurs when Windows Update fails to configure in short correctly download and install the update. When this happens, it will revert all the changes which are why you were advised to wait for a couple of hours. There are two possibilities why your computer is stuck on the “Preparing to configure Windows, Don’t turn off your computer” screen. The first one is that the Windows 10 operating system is installing any updates. The second one is when the user profile takes time to load or encounters an error. There are several options you can try to fix the problem. You can try running System Restore or boot your computer in Safe Mode or repair the corrupted profile via Registry Editor. You might also want to try using installation media to boot and repair your computer if the other options didn’t work.

Option 1 – Perform System Restore

• 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.

Note: If you can’t boot into the desktop of your computer, you can run System Restore in the Advanced Startup Options by following these steps:

• Boot your computer into the Advanced Startup Options screen.
• From there, you will see some options to troubleshoot when you can’t log in to Windows in the usual way.
• Now select Troubleshoot > Advanced Options > Command Prompt.
• After that, type “rstrui” and hit Enter to execute the command which will start the System Restore process.
• Once it’s done, restart your computer.

Option 2 – Boot your computer in Safe Mode

You can try to tap the F8 key if you have it enabled in your Windows 10 computer, as you start your system to boot into Safe Mode. Once your computer is in Safe Mode, you can access the Start Menu and the Mouse and Keyboard. Aside from that, you can also access your files and other built-in tools in Windows such as Command Prompt, PowerShell, Computer Manager, Device Manager, Event Log Viewer, and many more. On the other hand, if you haven’t enabled the F8 key, you can just go to the Advanced Startup options to boot your computer into Safe Mode. Once you’re there, select Troubleshoot > Advanced Options > Startup Settings > Restart > Tap the number 4 key. After that, your computer will restart in Safe Mode. If you want to reboot into Safe Mode with Networking instead, you can tap the number 5 key and for Safe Mode with Command Prompt, tap the number 6 key. Once your computer is in Safe Mode, you can use any of the built-in tools to restore your computer or troubleshoot the problem that’s causing your computer to get stuck at the “Preparing to configure” screen.

Option 3 – Try to repair your corrupted profile via Registry

In this third option, you can try to repair the corrupted profile using the Registry but before you proceed, take note that you can only try this if you can boot into your desktop and if you can, make sure to create a System Restore Point and then follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Then type “Regedit” in the field and hit Enter or click OK to open the Registry Editor.
• Next, go to this registry key: ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionProfileList
• Once you’ve opened the registry key, you should see a list of all the user profiles on your computer. Now click on each S-1-5 folder and look for the “ProfileImagePath” entry and double click on it to check which user account it is related to. You will see a path like “CUsersACK” where “ACK” is the username.
• You should know which of the user account is corrupted. Just look for a key named “RefCount” and change its Value data to “0” and click OK. And if it isn’t available, simply right-click on the right pane and create it.
• After that, double click on the key named “State” and make sure that the Value data is “0” and click OK.
• Exit the Registry Editor and restart your computer to apply the changes made.

Option 4 – Try to use installation media to boot and repair your computer

Another thing you can try to resolve the issue is to use the Windows installation bootable media so you can boot and repair the operating system. To use it, follow these steps:

• You need to first create an installation media which has the dame version of the operating system installed in your computer.
• After that, once you reach the Install Windows screen, click on the “Repair your computer” link.
• Wait until the repair is completed and then shut down your computer
• Now once your computer has restarted, check if it can now boot properly.

When trying to run Computer Management, or when running mmc.exe or compmgmt.msc from a command prompt you get the error that the application has been blocked for your protection then keep reading in order to solve the issue. This is a permission issue where if a regular user tries to run such system tools will result in saying that it has been blocked. Along with this, you may have a Group Policy issue. This can be fixed, but you will need admin permission to achieve it. It’s because when they are run from the command prompt with elevated privileges, it works.

1. Change Group Policy Settings

   If your account is an admin account, and you are still facing the issue, then change the group policy settings: Open Group Policy Settings by typing gpedit.msc in the run prompt followed by pressing ENTER Navigate to User Configuration > Administrative Templates > Windows Components > Microsoft Management Console > Restricted/Permitted snap-ins Locate Computer Management policy, and double click to open it Enable it, exit Group Policy. When Enabled: The snap-in is permitted and can be added into the Microsoft Management Console or run from the command line as a standalone console. When Disabled: The snap-in is prohibited and cannot be added into the Microsoft Management Console or run from the command line as a standalone console. An error message is displayed stating that the policy is prohibiting the use of this snap-in.

2. Temporarily disable UAC

   UAC is the user access control panel, and if you need to run the command right away, you can choose to disable it for some time. Click on the Start button, and then type UAC to find the User Account Control Settings. Click to open, and then slide down the notification setting at the bottom. It will temporarily allow launching the application as there is no check. However, make sure to switch to default once you are done.

Often when we connect to the internet were browsing indexed pages through some well-known search engine, usually Google. But beneath the so-called normal internet lurks deep and dark web. You might have heard of the deep web and dark web if you have some geeky friends and we are here to explain what exactly is the deep and dark web. The first thing to know is that the deep and dark web is not the same thing and they coexist separately from one another, you could say that beneath the deep web lies the dark web, yet another layer of the internet. So let us explore first the deep web. What is exactly a deep web?

Deep web, hidden web, or invisible web

as sometimes referenced are part of worldwide web not indexed by search engines, meaning that engines do not basically see and index content of deep web sites. The content of the deep web is hidden behind HTTP forms and includes many very common uses such as webmail, online banking, private or otherwise restricted access social-media pages and profiles, some web forums that require registration for viewing content, and services that users must pay for, and which are protected by paywalls, such as video on demand and some online magazines and newspapers. The content of the deep web can be located and accessed by a direct URL or IP address but may require a password or other security access to get past public website pages. While it is not always possible to directly discover a specific web server's content so that it may be indexed, a site potentially can be accessed indirectly (due to computer vulnerabilities). To discover content on the web, search engines use web crawlers that follow hyperlinks through known protocol virtual port numbers. This technique is ideal for discovering content on the surface web but is often ineffective at finding deep web content. For example, these crawlers do not attempt to find dynamic pages that are the result of database queries due to the indeterminate number of queries that are possible. It has been noted that this can be (partially) overcome by providing links to query results, but this could unintentionally inflate the popularity of a member of the deep web.

Dark WEB

The dark web is the World Wide Web content that exists on darknets: overlay networks that use the Internet but require specific software, configurations, or authorization to access. Through the dark web, private computer networks can communicate and conduct business anonymously without divulging identifying information, such as a user's location. The dark web forms a small part of the deep web, the part of the Web not indexed by web search engines, although sometimes the term deep web is mistakenly used to refer specifically to the dark web. The darknets which constitute the dark web include small, friend-to-friend peer-to-peer networks, as well as large, popular networks such as Tor, Freenet, I2P, and Riffle operated by public organizations and individuals. Users of the dark web refer to the regular web as Clearnet due to its unencrypted nature. The Tor dark web or Onionland uses the traffic anonymization technique of onion routing under the network's top-level domain suffix .onion.

Dark & Deep WEB difference

The dark web has often been conflated with the deep web, the parts of the web not indexed (searchable) by search engines. The dark web forms a small part of the deep web but requires custom software in order to access its content. This confusion dates back to at least 2009. Since then, especially in reporting on Silk Road, the two terms have often been conflated, despite recommendations that they should be distinguished. Darknet websites are accessible only through networks such as Tor ("The Onion Routing" project) and I2P ("Invisible Internet Project"). Tor browser and Tor-accessible sites are widely used among darknet users and can be identified by the domain ".onion". While Tor focuses on providing anonymous access to the Internet, I2P specializes in allowing anonymous hosting of websites. Identities and locations of darknet users stay anonymous and cannot be tracked due to the layered encryption system. The darknet encryption technology routes users' data through a large number of intermediate servers, which protects the users' identity and guarantees anonymity. The transmitted information can be decrypted only by a subsequent node in the scheme, which leads to the exit node. The complicated system makes it almost impossible to reproduce the node path and decrypt the information layer by layer. Due to the high level of encryption, websites are not able to track the geolocation and IP of their users, and users are not able to get this information about the host. Thus, communication between darknet users is highly encrypted allowing users to talk, blog, and share files confidentially.

Darknet

The darknet is also used for illegal activity such as illegal trade, forums, and media exchange for pedophiles and terrorists. At the same time, traditional websites have created alternative accessibility for the Tor browser in an effort to connect with their users. ProPublica, for example, launched a new version of its website available exclusively to Tor users.

As you know, every Windows Update is essential for every Windows operating system. They have to be regularly installed, especially since they include various security updates that are important to the system. However, there are times when Windows Update fails to execute properly and you get errors like the error code 0x80070BC9. When you encounter this particular Windows Update error, you will get the following error message on your screen:

“0x80070BC9 – ERROR_FAIL_REBOOT_REQUIRED. The requested operation failed. A system reboot is required to roll back changes made.”

This kind of Windows Update error is most likely caused by a newly installed problematic software, corrupted Windows Update files, or policies that restrict the behavior of the Windows Module Installer. The Windows Module Installer, also known as “WMIW” or “TiWorker.exe”, is the one that checks for new updates from the Windows server and installs them on your computer. This is why you need to make sure that you do not have any policies that control the start behavior of the Windows Module Installer since this service must not be hardened to any start value and should be managed by the operating system. To resolve the Windows Update error code 0x80070BC9, you can check out the options provided below.

Option 1 – Try checking the status of the Windows Modules Installer Worker Service

Since the Windows Update error code 0x80070BC9 has something to do with the Windows Module Installer Worker service, you need to check its status in the Service Manager. Refer to the following steps to do so.

• In the Cortana search box, type “services” and click on the Services icon to open the Services Manager. Alternatively, you can also tap the Win + R keys to launch the Run prompt and then type “MSC” in the field and hit Enter to open the Services Manager.
• After opening the Services Manager, look for the Windows Modules Installer Worker Service.
• Once you found it, check its status and make sure that its Startup type is set to Manual.
• Now click on the Start button and see if it fixes the Windows Update error.

Option 2 – Run the Windows Update Troubleshooter

You might want to run a built-in Windows Update troubleshooter to resolve the Windows Update error. It is one of the things you can check out as it is known to automatically resolve any Windows Update errors like error code 0x80072EE2. To run this troubleshooter, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 3 – Try contacting the IT administrator to modify the group policies

You could also try to contact the IT administrator to have the group policies modified. This option is applicable for company-managed systems. As mentioned, one of the possible causes of the Windows Update error 0x80072EE2 is the policies that control the start behavior of the Windows Module Installer. Thus, you need to have them removed so that the Windows Module Installer Worker service is managed by the operating system itself. And since there could be many policies, it is highly advised that you contact your company’s IT administrator to get the job done for you.

Option 4 – Try to install the Windows Updates in a Clean Boot State

There are some instances that some conflicting programs installed in your computer might be the one that’s causing Windows Update error code 0x80070BC9. To identify which program is causing the problem, you need to put your computer in a Clean Boot State. To do so, follow the steps below.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• From there, start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.

There are instances when you have to connect to another Windows 10 PC via remote connection from another Windows 10 PC. However, when you encountered an error saying, “Your password may have expired or the remote pc might not accept blank passwords” while doing so then read on as this post will walk you through how you can fix it. Here is the full content of the error message:

“Your password may have expired, or the remote PC might not accept blank passwords. Try connecting again. If this keeps happening, ask your admin or tech support for help.”

It is unknown what the exact cause of the error message is as it could involve several factors. Even so, there are still various potential fixes you can try to fix this kind of error. You can try to check if your password has expired or troubleshoot any issues with the network. You could also use a remote desktop application or configure the settings of firewall or restart the remote desktop service. For more details, refer to each one of the given options below. But before you proceed, make sure that you have someone to help assist you on the other side to help you troubleshoot the issue.

Option 1 – Try to check if the password has expired

The first thing you can do to fix the problem is to check if the password has expired as it could be the reason why you’re experiencing this problem. You have to make sure that you are using a user account that is on the remote computer and then check if the user account password has not expired yet. And if your PC is not within your access, then you can just ask someone to verify the password for you.

Option 2 – Try to troubleshoot network issues

To troubleshoot network-related issues that might be the one that triggers the error, you need to run the Network Troubleshooter. To get started, 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 use a remote desktop software

A number of users reported that the issue occurred when they used the universal app for Remote Desktop and they were able to fix it by switching to the Remote Desktop application. Thus, you can try to switch to the remote desktop software and see if it fixes the problem or not.

Option 4 – Try to configure Firewall settings

You might also want to configure the settings of the Firewall as it could also help in fixing the problem. It is possible that the firewall is blocking the incoming connection on the remote computer. To check if whether the firewall is the culprit or not, follow the steps below.

• Go to Windows Security and then go to Firewall and network application.
• Next, click on the Advanced Settings link. This will open the classic Windows Defender Firewall and Advanced Security application.
• From there, look for the rule named “Remote Desktop – User Mode (TCP-In)” under inbound rules and check if it has been disabled or not.
• If the rule is disabled, you have to enable it.
• Once done, check if the error is now fixed or not.

Option 5 – Try to restart the Remote Desktop service

If none of the four given options given above worked, you might want to restart the Remote Desktop service as it can help you in fixing the problem. To do so, follow these steps:

• Tap the Win + R keys to open the Run dialog box and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• Next, from the list of services, look for the Remote Desktop Service and right-click on it, and then click on the Restart option.
• Once done, check it was able to fix the “Your password may have expired or the remote pc might not accept blank passwords” error or not.