Razer unveils their first internal PC hardware

What is Drwtsn32.exe Application Error?

Drwtsn32.exe (DrWatson Postmortem Debugger) is a process file from Microsoft Corporation that runs on Microsoft Windows Operating System. This file is digitally signed from Microsoft Windows Component Publisher- Microsoft Timestamping Service. This file is a type of executable file. It is useful to debug and creates log files when an error occurs during running or program execution. The information logged by DrWatson is used by technical support personnel to diagnose a program error for a computer running Windows. It creates log files in the following location C:Documents and SettingsAll UsersApplication DataMicrosoftDr Watson. However, when using Internet Explorer, MS Outlook or any other application on Windows, you can experience drwtsn32.exe application error. This error occurs when the drwtsn32.exe file crashes. The error is displayed as:

“DrWatson Postmortem Debugger has encountered a problem and needs to close” "drwtsn32.exe - DLL Initialization Failed" when shutting down

Solution

Error Causes

The ultimate reason behind ‘drwtsn32.exe application error’ is malware and viral infection. Malicious software can enter your PC through downloaded files , browsing on unsafe websites and phishing emails. These viruses can disguise themselves as DrWatson utility. Plus theymay have the same name as this process. However, the best way to detect if it is a virus is to track its location. Malicious software will usually hide in some other location instead of its standard location. However, other reasons for this error also include incompatible software and damaged system files.

Further Information and Manual Repair

a) Scan PC with an Anti-Virus

It is advisable to repair this issue right away especially if the underlying cause is a viral infection typically because viruses can expose you to privacy errors and risks such as cybercrime, identity theft, and data security issues. To resolve it, download a powerful antivirus. Scan your PC with it and remove all the viruses immediately. However, when doing so, you may have to compromise PC performance and halt other PC activities. Anti-viruses are notorious for slowing down PC speed. In addition to this, sometimes you may have to stop other activities on your PC for the antivirus to scan for viruses.

b) Repair Registry Errors with Restoro

Nonetheless, if the drwtsn32.exe application error is related to system file corruption, then this indicates registry issues where all the system data is stored. Registry issues occur if you don’t maintain your PC properly and let invalid, wasted and obsolete files accumulate on your PC. This damages and corrupts the system files and generates such error messages. To repair it, download a registry cleaner. However, the best alternative to resolve drwtsn32.exe application error in seconds whether the error is linked to registry issues or viral infection is to download Restoro. This is a multi functional PC fixer embedded with multiple utilities including a powerful antivirus, a registry cleaner and a system optimizer. It wipes out all the unnecessary files stored in the registry, repairs the damaged and corrupt system files and restores the registry. With the help of the antivirus, all privacy errors and viruses are scanned on your PC and removed immediately. And to ensure your system’s speed is not compromised, it also functions as a system optimizer and increases your PC’s speed significantly. The software is safe and efficient. It has simple navigations and a user-friendly interface which makes it very easy for all levels of users to work around. It is compatible with all Windows versions. Click here to download Restoro and resolve drwtsn32.exe application error today!

In case you don’t know, new support has been added by Microsoft to Windows 10 that now allows users to turn off or on the Mobile Hotspot remotely. The Mobile Hotspot feature, known earlier as “Virtual Networks”, was first introduced with the initial release of Windows 10. With this new feature to remotely turn on or off the Mobile Hotspot in Windows 10, users can just use the Bluetooth on their mobile phones to turn off or on the Mobile Hotspot even when their Windows 10 computers are out of their reach. To turn off or on the Mobile Hotspot feature in your Windows 10 computer remotely, there are two options you can try. First, you can do it using the Windows 10 settings app or using the Registry Editor. To get started, refer to the following options.

Option 1 – Turn off or on the Mobile Hotspot remotely via Windows 10 Settings app

• First, you need to open the Windows 10 Settings app and from there go to Network & Internet and then go to the Mobile Hotspot section.
• After that, scroll down to the “Turn on remotely” section.
• Once done, make sure that the toggle button is set to ON and that the Bluetooth of both devices is turned on and paired as well. This should enable the feature to turn on or off the mobile hotspot remotely.

Option 2 – Turn off or on the Mobile Hotspot remotely via Registry Editor

Before you get started with the second option, make sure that you create a System Restore point first. Once done, proceed to the following steps:

• Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and then hit Enter to open the Registry Editor.
• Next, navigate to this registry path: ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWcmSvcTethering
• From there, look for the DWORD named “RemoteStartupDisabled” and set its Value data to be “0”. This will enable the feature that will allow you to remotely turn on or off the mobile hotspot in your Windows 10 computer. To disable it, just set its Value data to “1”.

The Winload.efi file is an Extensible Firmware Interface or EFI file. EFI files are executable files for the firmware of the computers that are mainly based on UEFI and execute the tasks of loading the files to the bootloader of the computer. They are used for a specific set of tasks such as turning on the computer, installing Windows, restarting the computer or resetting it, and so on. This is why the Winload.efi file is a significant file so if it gets corrupted, lost, or damaged, it would be impossible for the Windows operating system to proceed. Here are some errors you can encounter that are related to the Winload.efi file:

• efi is missing
• efi cannot be found
• efi is missing or contains errors
• This program can’t start because winload.efi is missing from your computer
• This application requires the file winload.efi, which was not found on this system.
• There was a problem starting [path]winload.efi. The specified module could not be found.

In addition, the 0xc0000225 , 0xc00000e and 0xc0000001error codes are also associated with the Winload.efi file. Before you start troubleshooting the problem, you can try to perform System Restore first. This will help undo any changes you’ve made in your computer that might have triggered the Blue Screen error. To perform System Restore, here’s what you have to do:

• 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 your create a System Restore point first.

Option 1 – Try rebuilding the Boot Configuration Data (BCD) and repairing MBR

• Once you get to the Welcome Screen part, click on Next.
• Afterwards, 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, the following commands to rebuild BCD files and repair MBR. Don’t forget to hit Enter right after you type each command.
  • bootrec /repairbcd
  • bootrec /osscan
  • bootrec /repairmbr
• Once the command line is successful in finding out a Windows installation, hit Y to let it boot from the list which will successfully rebuild BCD.
• Now type “exit” to close Command Prompt and then restart your computer to successfully apply the changes made.

Option 2 – Disable the Secure Boot in the BIOS

Disabling the Secure Boot in the BIOS settings is definitely recommended to resolve errors related to the Winload.efi file. To disable Secure Boot, here’s what you have to do:

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

Option 3 – Run System File Checker scan

You might also try running the System File Checker or SFC scan to fix the error. System File Checker is a command utility built into your computer that helps restore corrupted files and missing files. Refer to the following steps to run it:

• Hit the Win + R keys 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 4 – Disable the Early Launch Anti-Malware Protection

• You need to restart your computer in the Start Menu first while holding down the Shift key on your keyboard.
• After that, it will restart your computer to Startup Settings.
• Now ensure that the 8^th option is labeled as “Disable early launch anti-malware protection.
• Then tap the F8 key since the aforementioned option above is listed at number 8. This should launch and load Windows on your PC with the Early Anti-malware protection disabled for that session only when you try to carry out the same task and then check if the error related to the Winload.efi file is now fixed.

USB Kill, a USB device is able to fry and damage your computer, mobile phone, router, etc. This device is quite dangerous and can kill electronics the moment it is inserted into an available port. By now people should know that they should not put unknown USB sticks into their devices because of potential virus and malware threats but this raises using unknown sticks to a whole new level.

Kill kits are not really new to the market, they have existed before but lately, technology really progressed and the latest USB sticks are really good, their success rate is around 95% which is pretty high and should not be taken lightly.

The second thing that you really should not play with strange USB sticks is that they dropped in price really hard, although top Kill kits will still go as high as around 300 USD, there are really cheap ones lurking in Ali Express that are just 6 USD!!! that makes them affordable devices for the mass market.

The device is made to take energy and current from the port it is plugged in, multiply it and release its charge back into the device, successfully frying some components immediately. Some more professional Kill sticks can even fry devices even when the device itself is not powered and can be even started remotely.

The point of this article is to make you aware that you should not in any kind of circumstances use and plug-in USB sticks into your devices that you do not know where they come from, especially from the mail!!

Error Code 10 - What is it?

Error code 10 is a type of Window Device Manager error code. This error code is generated when the Device Manager can’t start the hardware device or is experiencing device driver issues. It is displayed in the following format:

"This device cannot start. (Code 10)"

You can access complete details about error codes related to Device Manager such as code 10 through the Device Status area in the Device Properties.

By accessing Device Status, you can easily view the status of each device and learn about the specific device that could be causing the problem.

Solution

Error Causes

Error code 10 can be triggered due to several reasons. These include:

• Outdated drivers
• Corrupted drivers
• Incompatible drivers
• Device configuration issues
• Hardware compatibility problems

Device driver corruption can cause you great inconvenience and PC performance issues. The computer’s operating system relies heavily on device drivers to communicate with the hardware.

For example, the printer driver facilitates functioning of the printer. Similarly, the graphic card driver ensures proper video output on the monitor screen.

However, your PC hardware, such as printer or keyboard, may stop functioning properly if their device drivers become outdated or corrupt. Therefore to avoid inconvenience and to ensure your PC works properly, it is important to resolve the problem immediately without any delay.

Further Information and Manual Repair

To repair error code 10, you don’t have to be a technical whiz or hire a professional computer programmer. Here are some of the best and easy to perform DIY methods that can help you fix this device error in no time.

Method 1 - Reboot Your PC

Sometimes temporary problems in Device Manager can also generate code 10 error. Therefore it is advisable to restart your PC. Rebooting your system might fix the error. Try it! If it does, great, however, if the error still persists, then try other methods listed below.

Method 2 - Reinstall Drivers

Go through the Device Status in the Device Properties to view the driver causing the problem. If any driver is tagged with a yellow exclamation point, it means that driver is the one causing problems. Once identified, uninstall that driver and then reinstall it. This will hopefully resolve the problem.

Method 3 - Update the Device Driver

Whether the error code 10 is generated due to incompatible, corrupted, or outdated device drivers, simply update the device driver to resolve. To update the driver, go to the Device Manager, then click the driver tab in the device properties dialog box.

After that, click update driver. This will start the hardware update wizard. Then follow the instructions to update the driver on your PC. During this process, you may be prompted to provide the driver path.

If you don’t have it, then you will have to download the latest driver from the hardware vendor’s official website. This can be time-consuming and stressful.

Method 4 - Install DriverFIX

Another alternative is to install DriverFIX.  It is a user-friendly device driver management software with an intuitive interface.

Its intelligent algorithm is designed to detect all the problematic drivers in seconds. It automatically updates and accurately installs appropriate drivers and ensures your PC runs at its optimum level in no time.

Click here to download DriverFIX on your system to resolve error code 10.

Hal.dll Error - What is it?

Hal.dll error is a type of dynamic link library error that is common in Windows. Hal.dll is the critical file in all Windows installations and the error occurs when this file cannot be correctly loaded. Hal is the abbreviation for ‘Hardware Abstraction Layer’. Communication between Windows and different PC hardware is facilitated with this file. The error causes inconvenience and hampers your ability to use the hardware. The error message is displayed in either one of the following formats:

• "Windows could not start because the following file is missing or corrupt: C:Windowssystem32hal.dll. Please re-install a copy of the above file."
• "Cannot find WindowsSystem32hal.dll"
• "C:WindowsSystem32Hal.dll missing or corrupt: Please re-install a copy of the above file."

Solution

Error Causes

Hal.dll error occurs due to multiple reasons. These include:

• BIOS are not configured properly
• Damaged hard drive
• Hal.dll file is missing, damaged, or corrupt
• Viral Infection

Further Information and Manual Repair

To fix and resolve the Hal.dll error code on your system, you don’t always have to hire a professional technician for the job. Though Hal.dll error is critical but easy to resolve, here are some solutions that you can try to fix it right away even if you don’t have any technical expertise.

1) Restart Your PC

Sometimes this can be a temporary error, so try restarting your PC. If the error is resolved then that’s great. However, if it still persists, then try other solutions.

2) Change the Boot Order

The underlying cause for the Hal.dll error is often not properly configured BIOS; if this is the cause, simply change the boot order of the bootable devices like your hard drive. The BIOS setup utility is used to change boot order settings. This can be done by restarting your PC. Once you restart, press F2 to enter the setup. Now go to SATA operation and change RAID AHCI to RAID ATA. Save changes and then exit. By doing so, you will be able to re-configure the BIOS and resolve the error.

3) Use BOOTMGR

Another way to resolve is to update the volume boot code to use BOOTMGR. To do this, access advanced startup options, open the command prompt and type bootsect command and then press Enter. Run the command and then you’ll get the following message: C: (\?Volume{37a450c8-2331-11e0-9019-806e6f6e6963}) Successfully updated NTFS filesystem bootcode. Bootcode was successfully updated on all targeted volumes. After that close the command prompt. This is most likely to resolve the error.

4) Repair Registry With Restoro.

In case the error is still not fixed, then this means that the problem is bigger than you thought. It may be due to hard drive failure, viral infection, or sometimes because of hal.dll file corruption. In the event of these error causes, it is recommended to download Restoro. Restoro is an advanced, next-generation, and multi-functional PC repair tool embedded with numerous utilities like a registry cleaner, an antivirus, and a system optimizer. The registry cleaner utility:

• Scans for all registry issues
• Wipes out the unnecessary files saved in the hard drive like the junk files, cookies, internet history, and temporary files
• Cleans the disk
• Repairs damaged and corrupt files
• Restores the registry

The antivirus utility scans and removes all malicious software from your PC including viruses, Trojans, malware, adware, and spyware. Simultaneously, it also boosts the speed of your system. It is safe and efficient PC repair software. It has simple navigation and a user-friendly interface. Whether you are using Windows 7, 8 or Vista, it is compatible with all. It can also be used on Windows XP. Click here to download Restoro and resolve the Hal.dll error today!

Hello all the wonderful people and welcome to our new article where we take a little different turn than usual and discuss why keeping old electronics around the house is not such a good idea. We all have some drawer or in some bag around the house and in the end of the day if that electronic has battery inside it is probably not the smart thing to keep it.

So naturally, the question comes why it is a bad idea to have old electronics with batteries in them? Well unlike a battery failure with, say, some AA batteries jammed in the back of an old toy, the risk with a lithium-ion battery failing isn’t just some leaking and corrosion in the battery compartment, it’s a potential fire as the battery swells up and the gases (combined with the stored energy) turn the battery into a potential fire hazard.

Good thing is that the battery will not explode just like that, it will swallow over time and get bigger and bigger until the breaking point is reached and all the fire breaks lose. So if by any chance you have some old gadgets lying around you can check up on them and see if has swelling process started, if yes, dispose properly of that piece of the old device immediately.

How to keep old electronics

If you’re not ready to get rid of the gadget then it’s best to charge it properly for storage. Proper charging keeps the battery cells and circuits in optimum health.

While recommendations vary by manufacturer and application, the general consensus is that lithium-ion batteries should be charged to approximately 40%. (Some manufacturers recommend charging 50% or 60% instead.)

Really, the important part here isn’t the exact percentage. What’s important is ensuring that the battery is charged to roughly half capacity and not stored with a completely discharged or completely full battery.

Discharge rates on lithium-ion batteries in completely powered-off devices are very slow, but you should still plan to top off the charge every 12-18 months or so to keep it around 50%.

If you wanted to go above and beyond, a metal storage container with a snug lid on a basement shelf with a desiccant pack inside to control the moisture would offer optimum conditions.

What is Mscomctl.ocx?

Mscomctl.ocx is a Microsoft library Windows Common Controls file. The Mscomctl.ocx error occurs when this file is either lost or gets corrupt. The error is displayed on the screen when the user tries to run a program that is dependent on this file. It appears as:

“Component 'MSCOMCTL.OCX' or one of its dependencies not correctly registered: a file is missing or invalid”

Solution

Download Available to Completely Repair the Error Mscomctl.ocx

Error Causes

Installing and then uninstalling a large number of applications on the Windows operating system often corrupts or unregisters the Mscomctl.ocx library. This message will continue to appear on the screen until you re-register the library file again on your system.

Further Information and Manual Repair

You don’t need to have the sound technical knowledge or call a professional to resolve Mscomctl.ocx error on your PC. The Mscomctl.ocx error is easy to repair and can be fixed in a couple of minutes. Here are 2 solutions to repair the Mscomctl ocx error code on your system:

Cause: Error occurs because the Mscomctl ocx file is unregistered

Solution:

1. Go to the start menu and type ‘Mscomctl.oxc and press enter
2. Copy the ‘Mscomctl.ocx’ file and paste it in "C:WindowsSystem32" folder
3. Now click the start menu again and type ‘CMD’ in the search box. This will open your computer's command prompt.
4. Once this opens, type either of the following commands and then press enter. If you have a 64-bit operating system, then type: Regsvr32 "C:WindowsSysWOW64MSCOMCTL.OCX” and if you have 32-bit operating system, then you should type ‘Regsvr32 "C:WindowsSystem32MSCOMCTL.OCX"

By doing this, you will be able to register the Mscomctl.ocx file on your PC and then you will no longer receive Mscomctl.ocx error code.

Cause: Error code occurs because the Mscomctl.ocx file is missing

Solution:

1. First search for MScomctl ocx on your local drive to see if it is missing.
2. If the file is missing, then download the MScomctl.exe file from a reliable website.
3. Now extract the file to your C:WINDOWSsystem32 directory
4. Then click start and run.
5. Now type ‘REGSVR32 MSCOMCTL.OCX’ and press enter

Please note to implement any of the two solutions stated above, you will need administrator rights. If you have the administrator rights then only can you make the above registry changes. Therefore to make the following changes you will have to access the PC using the Administrator account. Simply follow the instructions given above to repair this error code problem right away!

This post will guide you through fixing the INTERNAL_POWER_ERROR Blue Screen Error on your Windows 10 computer. If you encounter this kind of Blue Screen of Death error, this means that the policy manager experienced a fatal error which in turn means that it can happen because of Drivers or Software or even due to external hardware. And so to resolve the issue, here are some suggestions that might be of help.

Option 1 – Update the Device drivers

As mentioned, the INTERNAL_POWER_ERROR BSOD error might have something to do with the drivers. It could be that the drivers are outdated so you need to update them in order to resolve the issue.

• 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. If you see a red or yellow sign that shows up against the driver, right-click on the driver’s name and select “Update Driver Software” or “Uninstall”. And if you find any drivers with a label saying, “Unknown device”, you need to update them as well.
• Select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.
• Restart your PC.

Option 2 – Check the Device performance and health

You can also try checking the device's performance and health in the Windows Defender Security Center.

• Open the Windows Defender Security Center.
• From there, check if there is a yellow exclamation icon in the Device performance and health section.
• After that, click on the View report option and you might see Health Report that points towards Storage Capacity, Device Drivers, or Apps and Software which should give you an idea of what the root cause of the problem really is.

Option 3 – Try to run the Chkdsk utility

Running the CHKDSK utility might also help you resolve the INTERNAL_POWER_ERROR Blue Screen error. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the CHKDSK utility comes in. The CHKDSK utility repairs hard drive errors that might be causing the problem.

• Open Command Prompt with admin privileges.
• After opening Command Prompt, execute the following command and hit Enter:

chkdsk /f /r

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

Option 4 – Try increasing the size of the Hibernation file

• In the Cortana search box, type “command prompt” in the field, and from the search results that appear, right-click on Command Prompt and select “Run as administrator”.
• Next, type in the following command and hit Enter to execute it:

powercfg /hibernate /size 100

• Note that the default size of the Hibernation file is 75% and after executing the command, it should increase to 100%. Now exit Command Prompt and check if the problem’s now fixed or not.

Option 5 – Try to run the troubleshooters

Blue Screen Troubleshooter:

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

Performance Troubleshooter:

• Tap the Win + R keys to open the Run dialog box.
• Type “msdt.exe /id PerformanceDiagnostic” in the field and hit Enter to open the Performance troubleshooter.
• Then click on Next to get started. Wait until the process is completed.

System Maintenance Troubleshooter:

• Tap the Win + R keys to open the Run dialog box.
• Type “msdt.exe /id MaintenanceDiagnostic” in the field and hit Enter to open the System Maintenance Troubleshooter.
• After that, click on Next to start troubleshooting the problem and wait until it’s done then check if it fixes the problem or not.

Option 6 – Uninstall the programs you installed recently

Chances are, some programs that you just installed might be the one that’s causing the BSOD error. Thus, you need to uninstall the program to resolve the problem.

• In the search box, type in “control” and then click on Control Panel (desktop app) among the search results.
• After that, select Programs and Features from the list which will give you a list of all the programs installed on your computer.
• From there, look for the concerned program and select it and then uninstall it.

Note: If you have downloaded the app from the Windows Store, you can simply right-click on it from the application list and then uninstall it.

Option 7 – Run Windows Defender offline

You also have the option to run Windows Defender offline and scan your computer to see if any malware has infected the computer and the one that’s causing the INTERNAL_POWER_ERROR Blue Screen Error.

Universal Windows Platform (UWP) applications are the modern application in the windows store that can be used in all the Window devices like Xbox, Hololens, Tablet, PC or Phone. Basically, UWP provides a common platform for every device that runs Windows 10. When attempting to login into these applications and receive this error:

Can’t sign in with a Microsoft account This program is blocked by group policy. For more information, contact your system administrator. 0x8000704ec

Then this post is for you. We will guide you on how to easily resolve issues, please follow the steps provided.

1. Local group policy editor solution

   • Press ⊞ WINDOWS + R to open the Run dialog.
   • In the Run dialog box type gpedit.msc and press ENTER to open Group Policy Editor.
   • Inside the Local Group Policy Editor, navigate to the path below:
   Computer Configuration > Windows Settings > Security Settings > Local Polices > Security Options
   • On the right pane, double-click on Accounts: Block Microsoft accounts to edit its properties.
   • Under Local Security Setting tab, click on the drop-down and select This policy is disabled.
   • Click Apply > OK to save the changes.
   • Exit Group Policy Editor.

2. Registry editor solution

   As always, it is highly recommended to make a backup of the registry editor just in case that something goes wrong.
   • Press ⊞ WINDOWS + R to open the Run dialog.
   • In the Run dialog box, type regedit and hit ENTER to open Registry Editor.
   • Navigate to the registry key path below:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
   • At the location, on the right pane, identify the NoConnectedUser key. The key value might be set to either 1 or 3.
   • Now, double-click the NoConnectedUser entry to edit its properties.
   • Input 0 in the Value data field and hit Enter to save the change.