A Guide to Quick Fixing the Error Mscomctl.ocx

If you receive the error code 0xc000014C while you boot up your computer, then this post might be of help. This kind of error usually points to the Registry of your computer that might be corrupted. As a result, the operating system was not able to read the BCD file and throws the 0xc000014C error. The error code 0xc000014C is triggered when your computer encounters an error in the first booting sector. You might receive any of these error messages:

“Info: An error occurred while attempting to read the boot configuration data.” with File: as “BootBCD” “File: Windowssystem32configsystem Info: Windows failed to load because the system registry file is missing or is corrupt” “Info: The Boot Configuration Data for your PC is missing or contains errors.”

To fix the error code 0xc000014C when booting your computer, you can check out the suggestions provided below.

Option 1 – Try running System Restore in Advanced Startup Options

Since you probably can’t boot into your Windows 10 computer, you can try to run System Restore again in the Advanced Startup Options.

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

Option 2 – Try to rebuild the BCD files

You can also try rebuilding the BCD files to resolve error 0xc000014C for corrupted Boot Configuration Data

• You can start by booting into the installation environment for Windows 10 from an installation media.
• After that, click on Repair your computer and on the blue screen, select Troubleshoot and then select the Advanced options menu.
• From there, select Command Prompt and once you open it, enter each one of the commands given below by sequence.
  • bootrec /FixMbr
  • bootrec /FixBoot
  • bootrec /ScanOS
  • bootrec /RebuildBcd
• Once you’re done executing the commands given above, type “exit” to close the Command Prompt window and then restart your computer and see if it fixed error code 0xc000014c.

Option 3 – Try restoring the default and uncorrupt Registry Values

This option is a bit tricky as you have to be sure about what you are doing here. However, if you are not sure, you might want to seek out a technician to fix the problem for you. But if you can handle it, then carefully follow the steps below.

• You have to first physically remove the hard drive of the computer that’s not booting up. You can refer to it as Hard drive 1 and Computer 1, respectively.
• After that, you need to have another computer which you can refer to as Computer 2, and refer to its hard drive as Hard drive 2. Make sure that this second computer is working properly.
• Next, you have to attach Hard drive 1 to Computer 2 with the Hard drive 2 attached as well.
• After that, boot Computer 2 from Hard drive 2 where Hard drive 1 will act as the second storage unit.
• Then navigate to the following location in the System Partition of the Hard drive 2.

C:/Windows/System32/config/RegBack

• From there, you have to replace all the files. Once you’re done, shut down your computer and then take out the Hard drive 1 from Computer 2 and put it back to Computer 1 as the only hard drive.
• Now boot your computer normally and check if the problem is fixed.

In this post, you will be guided on what to do if the Recent Items are no longer visible in the Taskbar icons in Windows 10. This can be quite inconvenient especially if you work simultaneously on many files and documents together and would require you to visit them regularly to incorporate changes. Thus, if you find that the Recent items are not visible in the Windows Taskbar, read on. In order for the Recent Items to appear on the taskbar icons in Windows 10 again, there are four potential fixes you can check out. You can try to show the recently opened items via Settings or clear the cache of the recent items. You could also make some changes in the Windows Registry or use the Group Policy Editor. But before you proceed with these potential fixes, it’s best if you create a System Restore Point first just in case something goes wrong after you made changes in the system. The System Restore Point allows you to undo these changes and bring back the previous state of your computer. Thus, you need to create one and then carefully follow the given options below.

Option 1 – Show the recently opened items via Settings

The first thing you can do to fix the problem is to show the recently opened items through the Settings app.

• Open the Settings app and select Personalization.
• From there, select the Start option and scroll down until you see the “Show recently opened items in Jump Lists on Start or the taskbar” option.
• Make sure that its toggle button is turned on.

Option 2 – Try to clear the Recent Items cache

• Tap the Win + E keys to open File Explorer.
• Next, copy and paste this link on the address bar: %AppData%Microsoftwindowsrecentautomaticdestinations
• Once you’re in the given location, you should see multiple files. Now select all these files and completely delete them.

Note: These files are automatically recreated when you interact with the system like performing tasks such as opening apps or accessing files.

• After that, go to this next location: %AppData%Microsoftwindowsrecentcustomdestinations
• Once there, delete all of its files and restart your computer. This should resolve the problem.

Option 3 – Try making changes via Registry Editor

The next thing you can do to fix the problem is to apply some tweaks in the Registry by following these steps:

• Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and hit Enter to open the Registry Editor.
• Next, navigate to this registry sub-path: HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersion
• From there, select the Policies Explorer folder located in the left pane.
• Then move to the right pane and look for the “NoRecentDocsHistory” entry and right-click on it.
• Now delete this entry.

Note: This entry is the one that stores the Group Policy setting for “Do not keep the history of recently opened documents. The Group Policy adds this entry to the registry with a value of 1 if you enable the “Do not keep the history of recently opened documents” policy. On the other hand, if you disable the policy by setting it to “Not configured” or deleting it, the Group Policy will delete the entry from the registry, and the system will act as though the value is 0 – for instance, it keeps the history of the recently opened files in your computer.

Option 4 – Try to use the Group Policy Editor

• Tap the Win + R keys to open the Run utility and type “gpedit.msc” in the field and tap Enter to launch the Group Policy Editor.
• Next, navigate to User Configuration > Administrative Templates > Start Menu and Taskbar.
• Afterward, double click on the “Do not keep a history of recently opened documents” policy located on the right panel. This is the policy that lets you enable or disable recent items and frequent places.
• Now to enable the recent items, as well as the frequent places, feature, click on the “Disabled” or the “Not Configured” option.
• Once you’re done, close the Group Policy Editor and restart your PC.

Note: If you choose to enable this setting, the system and Windows programs will not create shortcuts to documents opened while the setting is in effect. Aside from that, they also stay but won’t display the existing document shortcuts and the system will empty the Recent Items menu on the Start menu and the Windows programs won’t also display shortcuts in the Start Menu. In addition, the Taskbar won’t also show the recently opened or frequently used folders, files, or websites.

Sysdata.xml Error Code - What is it?

To develop a good understanding of the Sysdata.xml error code, it is first important to learn what is sysdata.xml file and its function. Sysdata.xml is a type of XML file. The .XML file extension is an Extensible Markup Language file. XML-based formats have now become the default for many office productivity tools including Microsoft Office and LibreOffice. Furthermore, it has also come into common use for the interchange of data over the internet. Sysdata.xml error code usually pops up when .XML based applications are unable to run and crash while loading. This is a type of BSoD (Blue Screen of Death) error code. Common symptoms include:

• System freeze
• The screen turns blue
• Sudden system shut down

Solution

Error Causes

The Sysdata.xml error code is triggered due to multiple reasons such as:

• Faulty hardware
• Malware or viral infection
• Registry issues

No matter what the reason may be, it is advisable to fix this error code right away without any delays. This is a fatal error and can result in a system crash and loss of data. And recovering valuable lost data is the hardest.

Further Information and Manual Repair

Here are some of the effective and easy do it yourself methods to resolve this error on your system:

Method 1: Fix Faulty Hardware

Hardware issues may arise due to many reasons like manufacturing issues or voltage fluctuations. Electrical storms can cause power surges which may affect the hardware causing it to fail. The best way to resolve this is to download the latest drivers for the problematic devices or alter the device configuration in the BIOS setup program.

• To reconfigure the BIOS simply restart your PC and before Windows starts, press Del Key to access your BIOS.
• Now find the factory reset option.
• Select the option and press the button to load your factory defaults.
• After that save changes and confirm your selection.
• Reboot your PC to activate the changes.

Method 2: Scan for Viruses

Sometimes viruses and malware can disguise themselves in the .XML files which can cause them to get corrupted. To resolve the issue, it is advisable to download a powerful antivirus and scan your entire PC for viruses. Remove the detected viruses to resolve the Sysdata.xml error on your system.

Method 3: Repair the Registry

If the registry is not cleaned frequently, it loads with unnecessary and obsolete files like the junk files and cookies. These files clutter and damage the registry and eventually corrupt it and the important files like .XML files stored in it. To resolve the issue it is recommended to download Restoro. It is a user-friendly and powerful PC Fixer embedded with a registry cleaner. It scans your entire PC for registry-related errors and removes them immediately. It cleans the cluttered registry and restores the damaged files thereby repairing the issue right away. Click here to download Restoro.

If you got an error message saying, “Windows could not start the Windows Update service on Local Computer, Error 87. The parameter is incorrect” while you were trying to start the Windows update service on your computer, then this post could help you resolve the problem. Along with this error, you might also get any of these error codes such as 0x80240034, 0x80244019, 0x80070643, and so on. Aside from these error codes, you will also notice that the Windows Update service has been stopped. To fix this issue, here are a couple of suggestions that might help but before you go on, you need to create a System Restore point first.

Option 1 – Try checking Services Dependencies

Dependencies of a Windows Service in Windows 10 are when windows services depend on other services. Such is the case with the Windows Update service – it also depends on three different services such as the Remote Procedure Call or RPC service, DCOM Server Process Launcher, and the RPC Endpoint Mapper. Meaning to say, if two of these services are not working as expected, then the dependant service will also be affected. This could be the reason why the Windows Update service could not start.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “services.msc” in the field and hit Enter to open Windows Services.
• From the list of Services, look for the following services:
  • Remote Procedure Call (RPC) Service
  • DCOM Server Process Launcher
  • RPC Endpoint Mapper
• After you find these services, double click on each one of them and check whether the Startup type for all is set to Automatic and the Service status is set to Running or not.
• If the service status is not running, then click the Start button. Afterward, check if you can now run the Windows Update service.

Option 2 – Check the Background Intelligent Service and the Cryptographic Service

• Tap the Win + R keys to open the Run dialog box.
• Next, type “services.msc” in the field and hit Enter or click OK to open Services.
• From the list of Services, look for the following services and make sure that their Startup type is as follows:
  • Background Intelligent Transfer Service – Manual
  • Cryptographic Service ­– Automatic
• After that, check if the Service status of the listed services above is set to Running. If they’re not, click on the Start button to start these services and then check if you can now enable the Windows Update service or not.

Option 3 – Reset Windows Update components

If the first two options did not work then you might want to reset the Windows Update components manually. Follow the steps below to reset them.

• Open Command Prompt with admin privileges.
• After that, type each one of the following commands and hit Enter after you key in one after the other.
  • net stop wuauserv
  • net stop cryptsvc
  • net stop bits
  • net stop msiserver

Note: The commands you entered will stop the Windows Update components such as Windows Update service, Cryptographic services, BITS, and MSI Installer.

• After disabling WU components, you need to rename both the SoftwareDistribution and Catroot2 folders. To do that, type each one of the following commands below, and don’t forget to hit Enter after you type one command after the other.
  • ren C:WindowsSoftwareDistribution SoftwareDistribution.old
  • ren C:WindowsSystem32catroot2 Catroot2.old
• Next, restart the services you’ve stopped by entering another series of commands. Don’t forget to hit Enter after you key in one command after the other.
  • net start wuauserv
  • net start cryptsvc
  • net start bits
  • net start msiserver
• Close Command Prompt and reboot your PC.

Option 4 – Run the Windows Update Troubleshooter

If resetting the Windows Update components didn’t work, you could also try running the Windows Update Troubleshooter as it could also help in fixing any issues related to Windows Update including this one. To run it, 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 5 – Try removing a value from the Windows Registry

If running the Windows Update troubleshooter didn’t help and you receive a message instead saying, “Service Registration is Missing or Corrupt”, you can try to remove a value from the Windows Registry.

• Tap the Win + R keys to open the Run dialog box.
• Then type “Regedit” in the field and hit Enter to open the Windows Registry.
• Next, navigate to this path: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsSelfHostApplicability
• From this path, look for a value named “ThresholdOptedIn” and if you find it, delete it.
• Exit the Registry Editor and see if you can now enable the Windows Update service.

In case you don’t know, the Windows Registry contains a System Hive which is a core part of Windows. The Windows operating system store various settings, options, and configurations. And if you encounter a Device Manager Error 49 for a device then it means that the system hive has exceeded its size limit. Worry not for this post will provide you with possible solutions that can help you in fixing error code 49. You will see the following error message when you encounter error code 49:

“Windows cannot start new hardware devices because the system hive is too large (exceeds the Registry Size Limit), (Code 49)”

There are instances when it may so happen that the device or devices are no longer attached to the computer but they are still listed in the system hive of the registry. For instance, if you were removing hardware and application for years but they weren’t removed from the registry then the size of the system hive keeps on growing until it hits the maximum limit. As you know, making changes in the registry manually, no matter how knowledgeable you are on such things is not sage since the registry is not only important but also complex. In addition, the System Hive is also a permanent part of the Registry associated with a set of files that contain information related to the configuration of the computer on which the OS is installed. To resolve this error, you must remove or uninstall any hardware devices that are no longer in the system. In fact, the Device Manager hides them by default so you need to enable hidden or non-present devices. Follow the instructions given below to set the Devices Manager to display devices that are no longer connected to the computer. Step 1: Tap the Win + R keys to open the Run dialog box. Step 2: After that type in “cmd” and hit Enter to open the Command Prompt. Step 3: Type “set devmgr_show_nonpresent_devices=1” in the Command Prompt and hit Enter to enable the hidden devices option. Step 4: After that, exit Command Prompt and tap Win + X + M to open the Devices Manager. Step 5: After opening the Devices Manager, click on View and then select the “Show hidden devices” option. This will show you all the devices that are not connected to the computer but are still mentioned. Step 6: Next, select a non-present device and click Uninstall from the Driver tab. Step 7: After that, repeat what you’ve done on step 5 for any other device that you no longer use. Step 8: Restart your computer. You can check the device Properties dialog box in the Device Manager after you’re done removing all the useless devices, to check if the error is now fixed or not. Moreover, you can also try running the Hardware and Devices Troubleshooter as it can also help resolve hardware-related problems. To use it, refer to the steps below.

• The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
• After opening Settings, look for the Update and Security option and select it.
• From there, go to the Troubleshoot option located on the left-hand side of the list.
• Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
• After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.

It has been some time since the release of Diablo 2 resurrected and overall reception was pretty good. People are enjoying the old classic game in hi-def. resolution and with new and improved visuals. Sadly some server issues are present still until this day and somewhat spoil the experience for players. The greatest lag and server crashes are pinpointed to game-creating events. When a player creates a new online game, the server needs to pull a lot of details from the database and make a game, due to some legacy code present this process takes some time and it is demanding a bit on the server-side, and although code was optimized to cater to more modern approach some legacy code still remains. Another thing that was spotted to affect performance itself is player behavior, to be more specific, modern gamer behavior. Where players find good builds and runs on the internet and then go to farm-specific areas or bosses for loot or experience points, which in return boils down to making plenty and short runs that are made by creating games and after run eliminating them. Now pair that with the previous statement about legacy server and database code and you can add 1 and 1 and see how this might be an issue. A lot of short games over legacy code are placing games in a state it was not designed for back in 2001 and therefore we have issues. Sadly solutions without completely rewriting the whole code are not very promising and they include rate limiting, which will prevent players to create many games in succession in a short period of time and maybe even login queues to drop a load on servers. Blizzard reached to people in the whole company, even old diablo 2 developers to ask for advice and they say that they are working on solutions so they could lift limitations and have everything running fine.

We have all experienced Windows errors over time and that can range from simple ones that will do very little to no harm and can be even system breaking making us lose our work or completely making the PC unusable. No one likes them but they happen, and usually, they happen once we least expect them.

No matter how frequent and unpleasant they might be there are ways to keep them at the minimum and even avoid them.

We will discuss steps that you can take in order to do this, simple tips and guides on how to keep your computer in top form and eliminate not just Windows, but any kind of errors altogether.

Keep your hardware clean

Believe it or not, some serious Windows errors like the dreaded blue screen of death can come from hardware issues not from the software at all. It is very important to keep your computer clean and with enough air flow so it can function properly.

Not so far ago we had an article about cleaning your hardware detailing what and how to do it. Here is a link to the article: https://errortools.com/windows/cleaning-your-pc/

Do not keep applications you are not using

Keeping applications on the drive might seem harmless but sadly that is not the case. Some applications have a certain impact on the system itself after all most of them are tweaking registry entries in Windows and sometimes having too many applications means an increased possibility of conflict over certain resources even when they are not running.

Some applications like adobe creative suite, for example, will have certain services always running in the background, and more of these kinds of applications you have, more services, more places for unexpected errors when they collide. Some of them will also install certain dependencies that could be problematic.

The general idea is: if you are not using it, uninstall it and you will be safer and more resilient to errors inside OS.

Do not use pirated or cracked software

Besides moral and law implications that using pirated or cracked software might bring you there are also certain other things that might be problematic. Certain "free" software might come packet with some problematic malware, for example, it is not uncommon for attackers to use some popular software to pack their malicious application with it.

Other things might be wrong and incomplete tweaking with application in order to bypass security and thus bringing some instability due to scripts needed to run in order to achieve this goal.

Keep your drivers updated

Errors can also come from old drivers or bad drivers, device manufacturers are not all-knowing and perfect, and sometimes drivers can wreak havoc on the system. Having updated drivers can minimize any kind of unexpected behaviors inside the operating system making it more stable and reliable.

You can check your driver version in the control panel inside the Windows OS and then compare it to the ones found on the manufacturer's site, if there are newer available it is recommended to download and install them,

Keep software updated

Applications can have bugs, and bugs can lead to certain errors both in the system and when using the app as well. It is in your best interest to get the latest patch or newer version of the software in order to avoid these unpleasant experiences.

Also, certain codecs and extensions that are installed directly in Windows can also have some unpredictable behavior, updating is the best solution to keep them in line.

Keep Windows updated

Same as with drivers and applications, Windows itself is not immune from bugs and some unpredictable issues. Luckily Microsoft is always working on fixes and features of Windows but in order to actually have benefited from that work, you will need to keep Windows updated. Sometimes a bad update can introduce some errors but you can always roll back to the previous and wait for them to fix everything and then download them all.

Check the health of your hardware regularly

Hardware components have their life cycle, more quality ones tend to last longer but eventually, they will reach the end of their lifecycle. There are a lot of testers for various components in your computer that can check different things and provide you with information about the state of your components.

If you are on Windows 11, Microsoft has included a basic health app inside OS, just type PC health check in search and start the app. For some more detailed information and advanced checks, you will have to use a custom application. There are plenty of them specialized for single components like RAM, SSD, etc. A simple google search with providing you with top results and most of them are free for personal use.

Remember, a faulty component or component that is reaching its life cycle can produce many errors inside the operating system.

Error Code 0x8007007B (Code 0x8007007B) – What is it?

Error code 0x8007007B (Code 0x8007007B) is an error that occurs when you attempt to activate Windows 10, as well as Windows Server 2008, Windows Vista, Windows 7, Windows 8, or Windows Server 2012.

Common symptoms include:

• You will see an error message like this: “Error 0x8007007B 'The filename, directory name, or volume label syntax is incorrect”.
• If you are using volume-licensed media to install: Windows 7, Windows 8, Windows Vista Business, Windows Vista Enterprise, Windows Server 2008 R2, Windows Server 2008, Windows Server 2012, Windows 10.
• Your computer is not connecting the activation wizard to a Key Management Service (KMS) host computer.

Solution

Further Information and Manual Repair

Error Code 0x8007007B usually occurs when a product key has been activated too many times. Blocking activation aids in avoiding abuse of the key. If abuse of the key is not the case, it is possible to get the key reset, or you may receive a new key altogether. When you are not sure that you can complete these methods yourself, as they do contain advanced steps, it would be wise to consult a computer repair technician to avoid making the problem any worse.

Generally, the solution can be simple; it is just dependent on how comfortable you are with getting technical in your computer. Volume licensed media means that the media has a preset number of times that it is allowed to be activated. This helps to avoid misuse of the product. Some people install the Windows 10 program multiple times on their computer if they are software developers or do certain types of software testing. It is important to know the cause in order to effectively find the solution.

Method One:

1. From the desktop screen, press the Windows key and S, type “Command Prompt”. Then, right-click on Command Prompt in the results. Select Run as Administrator.  Click Yes when asked about requesting permission.
2. In the Command Prompt box, enter the command: slmgr.vbs -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
3. The x's represent the product key. Replace these with your unique product key.
4. Type in the following command into the “Command Prompt” window: slmgr.vbs -ato
5. Click Enter
6. Restart your computer and try to activate windows again. It should not show the error code anymore.

Method Two:

1. While on the desktop, press the Windows key and R.
2. A window saying Run should open.
3. Type in the following command: Slui 3
4. Press ENTER and a window should appear.
5. This window asks for you to enter the operating system activation product key.
6. Enter this key in the space provided.
7. After entering this, click Activate.
8. Restart your computer now.
9. Check for activation. The Error code should be gone now.

Method Three:

1. Open the Command Prompt with access as administrator just as in Method One, and enter the following command: sfc /scannow
2. The command will complete the tasks. This will take some time so just let the computer do its thing and work. Let the sfc finish the scan.
3. When the scan is complete, restart the computer.
4. Check for the activation. The error code should be gone at this point.
5. If it is gone, revisit Method One or move on the Method Four.

Method Four:

Call the Microsoft Support Team and explain the problem in as much detail as you can give. Give the team the error code 0x8007007B and ask to have a different product key. When they give you the new product key, repeat Method 2. The Microsoft Support Team will either change your product key, or they will reset your current product key so that it can be used for activation again.

There are times when you try to open a file, an executable file for instance, but were unable to do so since you encounter an error in an Open File – Security Warning dialog box that says, “This publisher has been blocked from running software on your machine, You must unblock this publisher to run this software”. This kind of error is most likely thrown by your operating system because it considers the file to be unsafe and could potentially harm your computer. However, if you’re certain that the file is harmless, read on as this post will walk you through fixing the error so you can open the file without getting an error. There are various options you can check out to fix the error. You may run the program using Command Prompt or unblock it using File Properties. You could also try turning off SmartScreen or use the unblock file command in Windows PowerShell.

Option 1 – Try running the program via Command Prompt

• Tap the Win + R keys to open the Run dialog box and type “cmd” in the field and hit Enter to open Command Prompt.
• Next, tap the Shift key and right-click on the program or the executable file, and then select the “Copy as path” option.
• After that, paste this path in the Command Prompt window and tap Enter to open the program.

Option 2 – Try to unblock the file using File Properties

• Right-click on the file you were trying to open and select Properties.
• Next, click the Unblock button and then click on the Apply and OK buttons.
• You should now be able to open or access the file without getting the error.

Option 3 – Turn off SmartScreen

The next thing you can do is to turn off SmartScreen temporarily. All you have to do is open the Windows Defender Security Center and from there, go to the App & browser control section. After that, click on the radio button for Off under Check apps and files. Once you’re done, try opening the file again. Don’t forget to enable the SmartScreen back on.

Option 4 – Try to use the Unblock-File command in PowerShell

You might also want to utilize the Unblock-File command in Windows PowerShell as it will unblock the file so you can open it. To execute this command, follow these steps:

• Tap the Win + X keys and then click on Windows PowerShell.
• After opening PowerShell, type or copy and paste this command and tap Enter to execute it: Get-ChildItem -Path 'C:Users<username>Downloads' | Unblock-File
• The command you entered will unblock all the files in the Downloads folder, assuming that’s where the file you were trying to open is stored. If it’s not, then replace the path with the path where the file is located. Take note to also replace “<username>” with your Username.
• Now check if the file has been unblocked by accessing or opening it.

One of the useful features that came with Windows 10 is the Mobile Hotspot although there’s a downside to it – it drains your battery faster especially if your Windows 10 device is running on battery. Another one of its flaws in the implementation of this feature is that it stays activated even when the connection is idle. In other words, it is still activated even if no devices are connected to it. As a result, it consumes battery life and affects it. There are also instances when it affects the performance of the network connection. At the time of writing, Microsoft hasn’t done anything about this dilemma yet so in the meantime, you can continue reading this post to resolve this issue on your Windows 10 device. You can remedy this Mobile Hotspot issue by running a command in Windows PowerShell. To get started, follow the given instructions below.

Turn off Mobile Hotspot Automatically:

Step 1: The first thing you have to do is to copy the following command:

powershell -windowstyle hidden -command "Start-Process cmd -ArgumentList '/s,/c,net stop "icssvc" & REG ADD "HKLMSYSTEMCurrentControlSetServicesicssvcSettings" /V PeerlessTimeoutEnabled /T REG_DWORD /D 1 /F & net start "icssvc"' -Verb runAs"

Step 2: After copying the command given above, open the Notepad app and paste the command you copied there and save it. And when saving it, select the “Save as” option and its File type as “All files”. Step 3: After that, put “TurnOnTimer.bat” as the file’s name and save it on your Desktop. Step 4: Once done, run the file you just created, and when a User Account Control or UAC prompt appears, just click on Yes. Step 5: After you run the file, it will run a series of scripts in a command line which will turn off the Mobile Hotspot automatically when idle. And that’s how you automatically turn off the Mobile Hotspot when your Windows 10 device is idle. On the other hand, if you want to undo the changes made, you can always do so using the steps provided below.

Turn on Mobile Hotspot:

Step 1: Copy and paste the following command in the Notepad app:

powershell -windowstyle hidden -command "Start-Process cmd -ArgumentList '/s,/c,net stop "icssvc" & REG ADD "HKLMSYSTEMCurrentControlSetServicesicssvcSettings" /V PeerlessTimeoutEnabled /T REG_DWORD /D 0 /F & net start "icssvc"' -Verb runAs"

Step 2: After copying and pasting the command, save it as “TurnOffTimer.bat” on the Desktop. Step 3: Once done, run the file like what you did earlier and select Yes when a UAC prompt pops up. This will run a series of scripts on a command line which will revert the changes back to their default state.