Fix BlueTooth issues in Windows 10

nslookup is a command-line tool that helps in finding the DNS records of a website. It sends a name server query to the DNS and obtains the corresponding IP address. Aside from that, it can also perform some complex functionality such as finding details about FTP server, Mail server and many more but most of them are used by administrators. The best thing about nslookup is that it queries the DNS server directly and it does not rely on the cache. On the other hand, there is another tool called PING that is used to verify connectivity. PING sends a packet of information to the IP address or Domain and gets back a response in the form of packets. So if everything goes well, all packets are received but if not, it will help you find out where the delay in the network exactly is. However, the ping command does not always attempt a DNS lookup which means that it might be using the DNS cache and use the IP address available in that table. Although both nslookup and PING help you in identifying the host or IP address, however, they don’t always work and sometimes fail. So if your nslookup works but ping fails on your Windows 10 PC when querying the IP address of a website then it could be caused by many reasons. It could be that the nslookup queries work for you but when you try to use PING, it fails. For instance, if you open the abc.com website, here’s how it will look like:

nslookup xyz.com Server: dns.company.com Address: 192.168.1.38 C:> ping xyz.com Ping request could not find host xyz.com. Please check the name and try again.

The domain is converted into an IP address and then data is sent to that IP address when you use PING. So when a reply comes back it means that the data is going back and forth to that domain without any problem. However, if the DNS fails to resolve the IP address of the website or if your PC does not attempt a DNS lookup, you will receive a similar error message that says, “Could not find host” and so on. To resolve this issue, here are some options that might help.

Option 1 – Reset Winsock, TCP/IP & Flush DNS

Resetting Winsock, TCP/IP, and flushing DNS might help you resolve the issue with nslookup and PING. To do so, follow these steps:

• Right-click on the Start button and click on Command Prompt (administrator) so you can pull up an elevated Command Prompt.
• After that, execute each one of the commands listed below. And after you typed in one after the other, you have to hit Enter.

1. netsh winsock reset – type in this command to reset Winsock
2. netsh int ip reset resettcpip.txt – type in this command to reset TCP/IP
3. ipconfig /flushdns – type in this command to flush the DNS cache

• Next, restart your PC and check if the problem’s fixed.

Option 2 – Force Windows to do a DNS lookup using FQDN

• Go to Settings > Network & Internet > Status > Change adapter options.
• From there, right-click on the network and select Properties.
• Next, in case you’re using IPv6, from the list of connections available in the list, select Internet Protocol Version 4.
• Then click on Properties and click Advanced.
• After that, switch to the DNS tab and select “Append these DNS suffixes (in order)” and click on the Add button and then add “.” as a suffix so that each time you query using PING and another tool, it will add a “.” at the end and will force the lookup.

Option 3 – Make sure that there is only one default gateway

If your computer has more than one NIC connected and there are multiple default gateways, then it will most likely create confusion which is why you need to remove the default gateway from the configuration of all NICs and make sure that there is only one default gateway.

Option 4 – Use the Google Public DNS

You might want to change your DNS to Google Public DNS as it could also help you in fixing the nslookup and PING issues. To do so, follow the steps below.

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

Option 5 – Check the Windows Host file

You can also try to cross-check the Windows Hosts file to find out if the website you are trying to open has been blocked, because if it is, then it’s no wonder why PING fails even when nslookup works. There are instances when some third-party application modifies the file and adds some websites to the blocklists. So if the website is indeed blocked, you need to remove it from the list.

Option 6 – Delete the WLAN Profiles

Deleting the WLAN Profiles might be a good idea if you are not able to connect to the internet on your computer and if you’re using Wi-Fi. It could be that the networks that were connected previously have gone rogue which is why it is not connecting properly. And so deleting the WLAN profiles might help you in fixing the issue with nslookup and PING.

Option 7 – Reinstall the Network Adapter Drivers

• Tap the Win + R keys to launch the Run window and then type in the “msc” command and hit Enter to open the Device Manager window.
• Under the Device Manager, you will see a list of drivers. From there, look for the Network Adapters and expand it.
• Then right-click on each one of the Network drivers and select “Uninstall device”.
• Restart your PC.

Despite popular belief, there are a lot of users running Linux OS. Linux offers great security and working environment and 96.3% of the world's top 1 million servers run on Linux. 90% of all cloud infrastructure operates on Linux and practically all the best cloud hosts use it. But gaming on Linux is limited, enter Steam proton a Valve’s gaming solution.

What is Steam proton?

Proton is a WINE fork with some extra capabilities, to play games and run applications not native and not made to run natively under Linux OS. It is supposed to bridge the Gaming issues for PC users and let them more freedom in choosing an operating system to game on.

Find out if your game supports Proton

Although there are a lot of titles that nowadays run natively on Linux some will still need proton in order to run at all and sadly some of them will not be able to run on Linux even via proton but seeing how Valve is busy and it is trying to push its ideas and technology slowly this gap is closing. In order to see how the game you want to play performs and behaves on Linux and proton environment visit https://www.protondb.com/ and find out. As soon as the site loads you will be greeted with statistics and a search option to find out the status of the desired game with one of the given statuses: Borked, Bronze, Silver, Gold, Platinum, and Native. As you probably guessed native means that the game will work on Linux out of the box and borked will probably not work at all. Platinum and gold status means that game will run on proton without any input or tweaks from the user while silver and bronze means that it will work but might need some tweaks in order to make it work.

How to get Steam proton?

In order to run games under proton inside Linux, you will need firstly a Steam client which luckily works naturally on Linux. Unlocking/activating Steam Proton on your Linux-based system is easy. Just head over to Steam > Settings > Steam Play and toggle the option “Enable Steam Play for Supported Titles”. Valve has tested and fixed some Steam titles and you will now be able to play those titles. However, if you wish to go even further beyond, and play titles that even Valve has not tested, toggle the option “Enable Steam Play for all titles”.

Conclusion

Even we are not there yet, native gaming on Linux is gaining a foothold each day. Will Steam’s OS with proton technology be one that will turn the tide from Windows or some other tech we cannot tell but one thing is for sure, more choices mean better products so I am hopeful for a bright future.

The Local Security Authority Subsystem Service or LSASS.exe is a process in the Windows operating system that is valuable as it enforces the security policy on the computer. Every time you log in to the Windows Server, the LSASS.exe is the one that handles the password changes and creates the access tokens while updating the security log. However, it is also frequently targeted by malware and is often imitated. The original location of this file is at “C:/Windows/System32” so if you open the Task Manager and notice that a process with a similar name has a different location then it is definitely a threat and is exploiting the security of your computer. To resolve issues related to LSASS.exe, here are some fixes that could help.

Option 1 – Use the Performance Monitor’s Active Directory Data Collector

Note that this option will only work on the recent Windows server versions. Refer to the steps below to use the Performance Monitor’s Active Directory Data Collector set on your computer.

• Tap the WINKEY + R button to open the Run dialog box.
• Then type “Perfmon.msc” in the field and hit Enter to open the Performance Monitor and from there open the Server Manager.
• Next, navigate to Diagnostics > Reliability and Performance > Data Collector Sets > System from the left side of the navigation bar.
• Then right-click on “Active Directory Diagnostics” and select Start from the context menu. This will take about 5 minutes or 300 seconds depending on the performance capabilities of your hardware to gather the data required and then take some more time to compile a report from the gathered data. Note that these timings are dependent on one another.
• After the report is compiled, you can find it under Diagnostics > Reliability and Performance > Reports > System > Active Directory Diagnostics. The report will contain all the information as well as conclusions. However, it does not mean that it will also contain the exact cause of the problem with LSASS.exe. Nevertheless, it should help you in fixing the problem.

Option 2 – Try to run the System File Checker

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files that might be the cause why the LSASS.exe file is having some issues. To run the SFC command, follow the steps given below.

• Type “cmd” in the Start search and then right-click on the appropriate search result.
• Next, select “Run as administrator” to open Command Prompt with admin privileges.
• 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.

 Now restart your computer and see if the problem is fixed or not.

Option 3 – Put your computer in a Clean Boot State

If none of the options given above helped, you can try putting your computer in a Clean Boot State as this can help you in finding any incompatible programs that’s causing the problem.

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

Once you’ve found any incompatible programs, you need to uninstall them. Refer to the steps below to do so.

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

Recently, a number of Windows 10 users reported an issue wherein they try to print from their PCs but were unable to and got an error message instead that states, “Port in use, please wait”. However, no matter how long they waited, nothing changed and they were still unable to print from their computers. On the other hand, when some of the users attempted to print wirelessly from their mobile devices, the printing continues which indicates that there is some issue between the computer and the printer. So if you are one of the users who are currently facing this problem, then this post should help. To fix this issue with your Printer, here are some possible fixes you can try that might work.

Option 1 – Run the Printer Troubleshooter

The first thing you can do to fix the “Port in use, please wait” error is to run the Printer Troubleshooter. This built-in troubleshooter in Windows 10 can help you fix most print issues. It checks if you have the latest printer drivers and then tries to fix and update them automatically. Aside from that, it also checks if you have connectivity issues or if the Print Spooler and the required Services are running fine. To run it, follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “msdt.exe /id PrinterDiagnostic” in the field and click OK or hit Enter to open the Printer Troubleshooter.
• Then click the Next button and follow the next on-screen instructions to fix the issue with the printer.

Option 2 – Try updating the Printer drivers

You might also want to try updating your printer drivers. All you have to do is locate the USB Composite Device. For complete details, follow the steps below.

• First, click the Start button and type “device manager”.
• Then click on the “Device Manager” from the search results to open it.
• From there, look for the USB Composite Device option and right-click on it, and select the Update Driver from the options.
• Restart your PC and then click the “Search automatically for updated driver software” option.

Note: You also have the option to download the latest version of your Printer from the manufacturer’s website.

Option 3 – Try selecting the correct port for your Printer

If the first two options given above didn’t work, then maybe it’s time to select a correct port for your printer since the wrong port has been selected which is why you’re getting the “Port in use, please wait” error.

• Open “Devices and Printers” from the Start search.
• Next, look for your printer from the list of devices and right-click on it, and then select Printer Properties.
• Now go to the Ports tab under the newly opened Properties window and make sure that the port type matches the connection on the list of ports currently in use.

Note: If your printer is using a USB connection then the port should have a USB or DOT 4 in its description but if your printer is using a network connection then it should have the following description:

• WSD
• Network
• IP

And if you notice that there are several listings for the same type of port, you have to change the selection to a different one and then click the OK button to save the changes made.

One of the popular tools that allow a user to offer or obtain remote assistance on a computer is the TeamViewer. It is available on all the major computer and mobile platforms which makes it a lot useful to every kind of user, even on the go. If you are one of the users who frequently use TeamViewer, then you must be familiar with this one sentence that states, “Initializing display parameters”. In common cases, this sentence will appear for a second and load the other user’s screen. However, some users reported that TeamViewer gets stuck on that stage and did not move ahead even a bit. If you experience the same problem, read on as this post will guide you in fixing this issue with TeamViewer on your Windows 10 computer. At the time of writing, the cause of this issue is still unclear. It could be due to the quality of internet connection, conflicts in process, misconfiguration of Remote Access, and many more. To fix this issue, you can try to update TeamViewer for both the users or have it reinstalled with Unattended Remote Access, or reconfigure the Remote Access. You can also try to kill any conflicting processes or optimize your internet connection. For more details, refer to the given options below.

Option 1 – Reboot your router

The first thing you can try to do to fix the error is to simply restart your router. All you need to do is reboot the router from its Admin panel or you can also turn it off manually and turn it back on after a couple of seconds so that it can completely reboot. Once you’re done, try accessing your server again and see if the error is now fixed.

Option 2 – Try to update TeamViewer on both users’ end

You might have to update the TeamViewer on both ends and to do that, you need to start the TeamViewer installer again. Once it is installed, run the program and click on the Help option in the Menu ribbon and then select the “Check for updates…” option. If an update is found, you will be notified within a couple of seconds through a pop-up mini window. From there, click on Update and then follow the next onscreen instructions that appear and choose your TeamViewer version to update.

Option 3 – Try reinstalling TeamViewer via the Unattended Remote Access

If the first two given options didn’t work, you might have to reinstall TeamViewer from the Windows 10 Settings app or Control Panel.

• Tap the Win + R keys to launch the Run utility and type “regedit” in the field and hit Enter to open the Registry Editor.
• Here, navigate to this registry key: Computer HKEY_LOCAL_MACHINE SOFTWARE Wow6432Node TeamViewer
• Next, look for the TeamViewer key and right-click on it, and select Delete.
• After that, restart your PC to apply the changes made and then start TeamViewer again, and then click on Connection > Open Management Console.
• Then sign in or sign up to get registered and select the Add new device radio button under Add > Add computer located on the top-right corner and then select the Download now option.
• Now follow the next onscreen instructions that appear to complete the installation and then check if it fixes the problem or not.

Option 4 – Try reconfiguring the Remote Access

You can also try to reconfigure Remote Access in case there is some misconfiguration that might have caused the problem with TeamViewer.

• On your Desktop, right-click on This PC and click on Properties.
• Next, go to the left side of the navigation panel and click on Remote Settings.
• From there, make sure that the “Allow Remote Assistance Connections to this computer” checkbox is checked under the Remote Assistance section.
• Once done, click on the Advanced button. This will open a new mini window where you’ll have to check the “Allow this computer to be controlled remotely” option under the Remote Control section.
• Then click on OK and see if it fixed the problem.

Option 5 – Try to kill any conflicting processes

• Tap the Ctrl + Shift + Esc key combination to open the Task Manager.
• Then navigate to the Processes tab and right-click on the BGInfo process.
• Now select the End Task option to kill its process and then start TeamViewer again and check if the problem is resolved.

Option 6 – Try to optimize the quality of connection

You need to take care of two things under this option – first, you have to disable the loading of the Wallpaper of the computer which is the one that you’re trying to access remotely. To do that, you have to select the Extras menu from the menu ribbon and then select Options. And under the Remote Control section, check the “Remove remote wallpaper” option. The next thing you have to do is to optimize the quality for the speed by selecting the “Optimize Speed” for the menu of Quality still under the Remote Control section.

Resize icons on desktop in Windows 10 in a matter of seconds! Hello everyone and welcome to today's quick tip. If you have ever been dissatisfied with icon size on your desktop and any of the default sizes like small, medium large, etc have not been appropriate know that there is a quick way to resize icons on your desktop in between sizes. All that you have to do in order to use this built-in feature is: Press and hold CTRL and scroll with the mouse. That's it! Find your appropriate size for icons and enjoy.

Logon.scr Application Error - What is it?

To understand Logon.scr application error, it is first important to understand the function of logon.scr. Logon.scr is an important file that is located in the Windows\System32 folder. It guarantees Windows systems stability. Logon.scr application error occurs when logon.scr file gets corrupt. It is a common system error that can happen in most Windows platforms. It usually pops up during system start-ups and when trying to launch certain programs. Some of the common systems of this error code include: system halt, freeze, no application icons are visible on the desktop, random blue screen of death and system performance decreases dramatically.

Solution

Error Causes

Two of the most common causes of logon.scr application error is:

• Corrupted and damaged logon.scr file
• Viral infection

It is advisable to fix this error code immediately because it leads to serious damages. It is fatal and can result in a system crash; therefore resolve it right away.

Further Information and Manual Repair

To resolve this issue on your computer you don’t have to spend hundreds of dollars to hire a professional for the job. The good news is that it can be repaired easily and does not require any technical expertise. Here are some of the most effective and easy DIY methods to resolve the error on your screens.

Method 1 - Replace the Damaged and the Corrupted Logon.scr File

Whether the file gets corrupted or is accidentally deleted, the best way to fix the issue is to download the Logon.scr file again from a reliable website and install in the following location C:\Windows\System32. Alternatively you can also get the file copy form another proper functioning computer by using flash drive if you don’t have an internet connection to download the logon.scr file online.

Method 2 - Restore Points by Applying System Restore of Windows

Another way to resolve this is to restore points to bring back your system to the previous state before the error occurred. To do this, simply click the start button and type ‘System Restore’. Now click System Restore in the result and click next. Select the restore point in the list and click the next button to proceed. To activate changes reboot your PC.

Method 3 - Scan and Remove Viruses

If Logon.scr application error still persists, then it could be due to viruses. To resolve, install a powerful anti-virus. Scan your entire PC and remove viruses.

Method 4 - Repair the Registry

Corrupt and damaged Logon.scr file also triggers issues with the registry. DLL files and other important files like Logon.scr application files may get damage due to too many bad and invalid registry entries. Registry stores all the activities performed on the PC including unnecessary files like junk files and cookies. If these are not removed timely, these files accumulate and corrupt important files. Therefore, to fix the error it is advisable to clean and repair the registry. The best way to go about is to download Restoro. This is a user-friendly and multi-functional PC Fixer deployed with a registry cleaner. It scans for all registry errors and removes all the invalid entries. It cleans the registry and repairs the damaged files thereby resolving the issue in seconds. Click here to download Restoro and resolve the Logon.scr application error now!

If you suddenly find the Windows Recovery Environment not working and you see an error message saying, “Could not find the recovery environment”, then you’ve come to the right place as this post will guide you on how you can fix it. In times when you can’t boot into the Windows Recovery Environment, there could be several reasons behind it. However, have you ever wondered where exactly the Windows Recovery Environment is in your computer? Windows initially places the Windows RE Image file in the installation partition during Windows Setup so if you have installed Windows in the C drive, you can find the Windows RE at the C:/Windows/System32/Recovery or C:/Recovery folder. Keep in mind that this folder is hidden and later on, the system copies the image file into the recovery tools partition to make sure that one can boot into recovery if there are any issues with the drive partition. The “Could not find the recovery environment” error mostly occurs if the Windows Recovery Environment is disabled or if the “Winre.wim” file is corrupted. Thus, to fix this error, you need to refer to the given suggestions below.

Option 1 – Try to enable Windows Recovery Environment

• In the Windows Start Search, type “PowerShell” and from the search results that appear, right-click on Windows PowerShell and then select the “Run as administrator” option to open it with admin privileges.
• Next, type the “reagentc /info” command and tap Enter to execute it.
• After that, if the output states that Status is enabled, then you’re all set.
• Now type the “reagentc /enable” command and tap Enter to enable the Windows Recovery Environment. You will see a success message at the end signifying that Windows RE is available.

Option 2 – Try to fix the corrupted or missing “Winre.wim” file

If the Winre.wim file is either corrupted or missing, you need to get a new copy of this file from another computer where the Windows RE is working. Once you’re able to get a new copy of the Winre.wim file, you have to set the image path to a new location. For more details, refer to these steps:

• First, type “Powershell” in Windows Start Search and right-click on Windows PowerShell from the results, and select Run as administrator.
• Next, execute the given command below to change the path of the WIM file to the new location. Note that the steps should be used when the file path of the Windows Recovery Environment is different from the usual spot.

Reagentc /setreimage /path C:RecoveryWindowsRE

• As mentioned, if the file is corrupted, you just have to get a new copy from another PC but before you do that, make sure that the WINRE on that computer is disabled (just enable it later on) and then place it in the C:/Recovery path and then set its path again using the command given above and then verify its path by executing the following command.

reagentc /info command

Note: Since the Recovery folder is hidden as well as the WINRE folder in it and you won’t be able to access them using the Windows File Explorer, you need to use the Windows PowerShell or Command Prompt so that you can access them.

Option 3 – Try checking and fixing the WinRE Reference in the Windows Boot Loader

The Windows Boot Loader is the one that determines if it has to load the Windows Recovery Environment. It could be that the boot loader is pointing to an incorrect location which is why you’re getting the error. To resolve it, you have to check and fix the WinRE Reference in the boot loader. How? Follow these steps:

• In the Windows Start Search, type “PowerShell” and from the search results that appear, right-click on Windows PowerShell and then select the “Run as administrator” option to open it with admin privileges.
• After that, execute the “bcdedit /enum all” command.
• Next, look for an entry in the Windows Boot Loader identifier set as Current and look for “recoverysequence” in that section and take note of the GUID.
• Ensure that the device and the osdevice items show the path for the Winre.wim file and that they are the same. If not, you need to point the current identifier to the one which has the same.
• Once you’ve found the new GUID, execute this command: bcdedit /set {current} recoverysequence {GUID_which_has_same_path_of_device_and_device}
• Now check if the error in the Recovery Environment is fixed or not.

Option 4 – Try creating a Recovery Media

You could also try creating a Recovery Media to resolve the error in the Windows RE. All you have to do is download the Windows 10 ISO file using the Media Creation tool and then create a recovery drive. Once you’re done, check if it fixes the problem or not.

Changing Taskbar location in your Windows 10 is an easy task but lately, Microsoft has removed the option to just drag it to one side of the screen and place it there, now in order to change location we need to do a little more work but do not worry it is not difficult at all. Right-click on the taskbar to open its properties menu in the menu, on the bottom choose taskbar settings. Once the settings dialog opens, on the right side locate the taskbar location on screen. Click on the dropdown menu and choose the desired location for the taskbar.

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.