Command prompt tips and tricks

This post will walk you through fixing the rtwlane.sys Blue Screen error. This kind of BSOD error belongs under the category of the “DRIVER IRQL NOT LESS OR EQUAL” Stop errors. If you encounter this kind of Stop error then it means that a kernel-mode driver tried to access pageable memory at a process IRQL that was too high. The main issue with the rtwlane.sys Blue Screen error has something to do with the Realtek PCI-E Wireless LAN PCI-E NIC driver. In other words, it has some issues with the wireless card of your computer which is built by Realtek. And since it this error concerns your wireless card, you might also experience some connectivity problems with your computer as the wireless card refuses to find any network connections and even randomly disconnects. To resolve this problem, you need to refer to the given options below.

Option 1 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like rtwlane.sys Blue Screen error. It can be found on the Settings Troubleshooters page. To use it, refer to these steps:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

Option 2 – Try to update or rollback your Network driver

If you have updated the driver software as of late and you suddenly got this BSOD error, you might have to roll back the device driver – in other words, switch back to the previous working version. To do that, follow these steps:

• 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.
• From the list of Network Drivers, look for “Realtek <Model> Wireless LAN 802.11n PCI-E NIC” and then right-click on it and select Update Driver.
• Restart your PC and see if it helped in fixing the BSOD error.

Note: If you see any of the following entries under the Network drivers, you might want to download their latest available versions from each one of their manufacturer’s websites.

• Realtek High-Definition (HD) Audio Driver
• Realtek Card Reader Driver
• Realtek Local Area Network (LAN) Driver

On the other hand, if updating the Network driver didn’t help, you can also try to roll back to its previous version.

• Open the Device Manager again and then look for Network Drivers.
• Next, select Realtek <Model> Wireless LAN 802.11n PCI-E NIC from the list of Network Drivers and then double click to open a new mini window.
• After that, make sure that you’re on the Driver tab and if you are not, just navigate to it then click the Roll Back Driver button to switch back to the previous version of the Realtek driver.
• Now restart your computer to successfully apply the changes made.

Option 3 – Try running the System File Checker Scan

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the Netwtw04.sys failed BSOD error. 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 with good system files. To run the SFC command, follow the steps given below.

• Tap Win + R 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.

As you know, Windows Update is the source for everything latest for Windows from Microsoft. Your computer receives essential updates frequently because of the Windows Update service and this Windows Update mechanism depends on various services such as Background Intelligent Transfer Service or BITS, Windows Server Update Service, Windows Update service, and many more. Although it may seem like a complex delivery system, it is a very efficient one. However, it is not without its issues as it still encounters errors every now and then. One of these errors is 80244019 which applies only to the Windows Server operating systems and to resolve it, you need to determine its cause. The Windows Update Error 80244019 is most likely caused by faulty and corrupted DLL files or Registry Entries, connectivity issues, and outdated configuration of Windows Update service on the client end. Moreover, the error can also be caused by malware or if a file is not found on the server. This error can lead to a number of system issues like Startup and shutdown issues, software installation errors, external devices connection, system lags, unexpected application, and program issues, and many more. To resolve the problem, refer to the options given below.

Option 1 – Restart some Windows Update services

The first thing you have to do is to restart Windows Update-related services. Refer to the steps below to do so.

• Open the WinX Menu.
• From there, open Command Prompt as admin.
• Then type in the following command – don’t forget to hit Enter right after typing each one of them.

net stop wuauserv net stop bits

• After entering these commands, it will stop the Windows Update Service and the Background Intelligent Transfer Service.
• Next, go to the C:/Windows/SoftwareDistribution folder and get rid of all the folders and files there by tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.
• Once all the contents in the Software Distribution folder are deleted, restart your PC and then go back to Command Prompt and input the following commands again.

net start wuauserv net start bits

 Since the folder has already been flushed, it will be populated afresh the instant your restart your computer and open Windows Update.

Option 2 – Try turning on the Data Execution Prevention or DEP

The problem might be caused by disabled Data Execution Prevention which is why you have to make sure that it’s turned on.

Option 3 – Run the Windows Update Troubleshooter

You might also want to run the Windows Update Troubleshooter as it could also help in fixing Windows Update Error 80244019. 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 4 – Try reconfiguring the Windows Update Settings

You can also try to reconfigure the settings in the Windows Update section to resolve the error.

• Tap the Win + I keys to open the Windows Settings.
• Next, click on Update & Security > Windows Updates > Update Settings and from there, click on the Advanced Options.
• After that, uncheck the “Give me updates for other Microsoft Products when I update Windows” option.
• Now restart your computer to successfully apply the changes made and then check if the Windows Update error is now fixed.

Option 5 – Try to manually install the Windows Updates

Windows Update Error 80244019 might be due to a Windows Update that has failed. So if it is not a feature update and only a cumulative update, you can download the Windows Update and install it manually. But first, you need to find out which update has failed, and to do so, refer to the following steps:

• Go to Settings and from there go to Update and Security > View Update History.
• Next, check which particular update has failed. Note that Updates that have failed to install will be displayed under the Status column which has a label of “Failed”.
• After that, go to the Microsoft Download Center and look for that update using its KB number and once you find it, download and then install it manually.

Note: You can also use the Microsoft Update Catalog, a service from Microsoft that provides a list of software updates that can be distributed over a corporate network. With the help of this service, it can be easier for you to find Microsoft software updates, drivers as well as fixes.

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.

What is Windows ImageAcquisition High CPU & Disk usage? The Windows Image Acquisition is the driver model in charge of the communication between the graphics hardware and the operating system. There are times when it causes high disk and CPU usage in Windows 10 systems which results in slow performance of the computer. To fix this issue, read on as this post will help you in addressing the problem. The cause of this problem might have something to do with the hardware or the drivers. And so if your computer becomes slow because of the Windows Image Acquisition process, here are some suggestions that might be of help. You can try to restart the Windows Image Acquisition service, run a System File Checker Scan, disconnect & reconnect imaging hardware as well as update and reinstall the drivers and updating the graphics drivers. For a complete set of instructions, follow the given options below.

Option 1 – Try restarting the Windows Image Acquisition Service

• Tap the Win + R keys to open the Run dialog box.
• Then type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• From there, look for the Windows Image Acquisition Service and check on its service Status.
• If the Service Status is blank, right-click on it and select Start. And if the service Status is Running right-click on it and select Restart. After that, check if your computer’s performance is now back to normal.

Option 2 – Try running a System File Checker scan

As you know, running a System File Checker scan can help in replacing missing files as well as repair the corrupted ones which might be the reason behind the problem.

• Tap Win + R 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.

• Restart your computer after the scan is completed.

Option 3 – Try disconnecting and reconnecting the imaging hardware and then update and reinstall its drivers

It could be that the hardware that calls for the Windows Image Acquisition service has some issues which are why disconnecting and reconnecting the imaging hardware like scanners, printers, cameras can help in fixing the problem. In addition, you can also boot your computer in a Clean Boot State so that you can find the problematic hardware by hit and trial method. Refer to the steps below to do so:

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

Option 4 – Try updating the Graphics drivers

• First, boot your computer into Safe Mode.
• After that, tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. From there, look for the Display Adapters and click on them.
• After that, right-click on each entry under the Display Adapters and select the “Uninstall Device” option from the menu.
• Now restart your computer.
• After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.

Note: You also have the option to go directly to the website of your graphics card manufacturers like NVIDIA, Intel, or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it.

If you suddenly encountered the PDC WATCHDOG TIMEOUT BSOD Blue Screen stop error with a bug check value of 0x0000014F, then it’s probably due to a system component that has failed to respond with the allocated period which prevents the system from exiting connected standby. This kind of Blue Screen error could be caused by both hardware and software components. To fix this Stop error, here are some possible fixes you can try that might help but before you proceed, make sure that you create a System Restore point first and boot your computer into Safe Mode with Networking.

Option 1 – Try to rollback, update or disable drivers

The next thing you can do to fix the PDC_WATCHDOG_TIMEOUT Stop error is to roll back, or update, or disable device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

• Open the Devices Manager from the Win X Menu.
• After opening the Device Manager, look for the device driver named “IDE ATA/ATAPI controllers” and expand it.
• Then look for the SATA AHCI Controller entry and right-click on it. If you haven’t updated this driver in a while, select the “Update Driver” option. On the other hand, if you’ve just updated this driver, then select the Uninstall Device option.
• Next, follow the screen option to update or uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically if you have chosen to uninstall them.

Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Option 2 – Try to disconnect or disable newly installed hardware

In this option, you will have to disable or remove the hardware you’ve just installed recently since external devices could be the one that’s causing the Blue Screen of Death error to appear. To do that, just disconnect any external device that’s connected to your computer physically and then check if it fixes the PDC_WATCHDOG_TIMEOUT Blue Screen error.

Option 3 – Try running the Memory Diagnostic Tool

The Memory Diagnostic tool in windows can help resolve the PDC_WATCHDOG_TIMEOUT Blue Screen error by checking and automatically fixing any memory-based issues. To run it, refer to these steps:

• Tap the Win + R keys to open Run and type mdsched.exe and hit Enter to open the Windows Memory Diagnostic Tool.
• After that, it will give two options such as:
  • Restart now and check for problems (Recommended)
  • Check for problems the next time I start my computer
• Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.

Option 4 – Try to update the BIOS

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

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

Option 5 – Try running the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like PDC_WATCHDOG_TIMEOUT. It can be found in the Settings Troubleshooters page. To use it, refer to these steps:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

If the display of your Windows 10 computer turns on all of a sudden no matter how put it to sleep over and over again, it always wakes up, read on as this post will guide you in resolving this peculiar issue. In case you don’t know, the Windows 10 computer Sleep state is made in such a way that if it’s really important, it wakes up. You may have configured this kind of behavior or there could be some hardware component that’s interrupting its Sleep state. Thus, this post will give you some troubleshooting tips to fix the Sleep state issue caused by the Legacy Kernel Caller. The Legacy Kernel Caller points to the external hardware that’s causing your Windows 10 to wake up even when it’s in a Sleep state. Step 1: Find out what’s keeping your computer from going to sleep. To figure out what really is keeping your computer from going to sleep, you can execute the “powercfg –requests” command instead of checking the power configuration of your computer. This command will look for requests from applications and drivers that prevent the computer from turning off the display or from going to sleep. To execute the command, simply open Command Prompt and type “powercfg –requests” and hit Enter. After that, you will see part of the result that looks like this:

“SYSTEM [DRIVER] USB AUDIO DEVICE An audio stream is currently in use [DRIVER] Legacy Kernel Caller.”

Step 2: The next thing you have to do is remove all the external hardware connected to your computer. In this step, you have to disconnect external hardware from your computer. Based on reports from users who experienced the same issue, the “TV card” is the culprit so make sure you remove that one. Once you’ve removed it, open Command Prompt and run the “powercfg –requests” command again and you’ll see that the “Legacy Kernel Caller” will no longer be on the list. In addition, your computer will get into its regular sleep mode once the hardware is removed. Once you do that, the driver gets hung and won’t release the power request despite being used. Step 3: Try using the request override option The powercfg command also offers a request override option which allows users to disable the requests from applications and services to wake the computer from sleep mode. To run this command, simply open Command Prompt with admin privileges. After you open Command Prompt, type the following command and hit Enter to disable requests from applications and services that causes the computer to wake from sleep state.

Powercfg -requestsoverride Driver "Legacy Kernel Caller" System

Step 4: Check the streaming and media applications You also have to check if your computer is running an audio or video service in the background. In such cases, your computer won’t be able to go to sleep mode if these services are running in the background. You might have noticed that when you play a video or audio, your computer never goes to sleep. And if you have put it to sleep in between watching the video, then it’s probably why your computer is waking up. Thus, you have to stop these services. Step 5: Check the devices that can wake your computer If you didn’t see the Legacy Kernel Caller in the result after you execute the ”powercfg –requests” command, then you can try to execute the following command instead.

powercfg –devicequery wake_armed

After you enter this command, it will give you a list of all the devices that can wake your computer. So if there is anything other than the mouse, keyboard, touchpad, you have to check the power configuration of that device. To do that, go to the Device Manager and disable the device’s “Allow this device to wake the computer” option in its Properties Step 6: Check the Sleep Advanced Settings

• Click on the Windows key and type “control panel” in the field and select the related search result.
• Next, select the Security and Maintenance option and click on the Power Options.
• After that, you have to select the Change Plan Settings but keep in mind that this option is barely readable so you need to read each option carefully.
• Now click on the Change advanced power settings button and a new window will appear.
• Then look for the “Sleep” option and expand it. Make sure that the “Allow hybrid sleep” option is on.
• Reboot your computer and check if your computer now functions properly. If it still didn’t work, you may have to reverse the changes you’ve made.

On the other hand, you could also run the Power Troubleshooter to resolve the Sleep state issue. This built-in troubleshooter will automatically fix any power-related issues in your computer.

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.

PrintNightmare vulnerability has been a struggling issue for Microsoft in the past weeks, each time it seems to be addressed and fixed something new popped up and it still had issues. Microsoft finally addressed the issue but with a price. The default behavior of Point and Print is changed. From this fix onward, the Point and Print driver installation and update behavior will require administrator privileges, which should prevent the exploit to the Windows Print Spooler that could be used by malicious individuals to gain administrative privileges in Windows. The drawback of this fix from Microsoft is that non-elevated users may have difficulty adding or updating printers. Microsoft feels that the security risks caused by PrintNightmare are worth the tradeoff, though. If you really want to let non-elevated users add printers, you can follow the instructions in this Microsoft Support article to disable this mitigation with a registry key. However, doing so will expose you to this known vulnerability and isn’t recommend.

The new thing from Mozilla is not a browser, it is a VPN!

Besides Firefox, Mozilla offers now Firefox Relay, an app helping you to mask your email and phone number, and a new Mozilla VPN.

Mozilla has recently announced a new subscription model that will let you use all products together for $6.99 per month. Although this is a little more expensive than the competition that goes around for $5 per month note that with this subscription you are having access to all services, not just VPN.

VPN will not only hide your IP address but will also make sure websites cannot access your real location and it encrypts all of your network activity. Relay will give you protection against spam, serving as a shield for your email and limiting spammers from access to your real email address and phone number. With Mozilla subscription will let you use both services.

Windows Setup in Continuous Reboot Loop – What is it?

After upgrading to Windows 10 operating system from Windows 7 or Windows 8/8.1, a lot of Windows users are complaining about the Windows setup in a continuous reboot loop. The computer would just keep on rebooting every time the machine is booted and this incites frustration for a lot of Windows users.

Solution

Error Causes

When Windows launched the third update for Windows 10, users trying to upgrade to Windows 10 encountered an endless reboot loop problem. The computer will crash repeatedly. The KB3081424, which is a roll-up of bug fixes of Windows 10, continuously fails once you start the update process and then triggers a message showing: “We couldn’t complete the updates, undoing the changes.” The undoing process will then cause a system reboot mandatorily.

Once you log back on your computer again, the Windows 10 update will try to reinstall KB3081424. You will not be able to stop the update which will cause your Windows setup in a continuous reboot loop.

The KB3081424 will not be successfully installed since if it fails for the first time, that initial failure can be detected to create a bad entry in your Windows 10 registry. This will then prevent your subsequent attempts to reinstall KB3081424 to make it work correctly.

Further Information and Manual Repair

In order to fix the problem of Windows 10 setup in a continuous reboot loop, there are a few methods you can try. Try following these simple steps and you’ll be able to get rid of the problem.

Note: If you’re not highly confident to solve this issue on your own, it is highly recommended to consult an authorized computer technician who would be knowledgeable enough to fix the issue for you. In addition, you can also use a system optimizer to resolve the issue.

Method One: Check For Windows Update

Microsoft Windows released an updated fix for the Windows setup in continuous reboot loop problem. You can try fixing the issue through Windows Update.

1. Open Settings
2. Go to Update & Security
3. Select Windows Update then choose Check for updates

At this point, an additional update will be installed and downloaded to your operating system to resolve the continuous reboot loop problem.

Method Two: Eliminate Bad Registry Entry

Before KB3081424 attempts to install again, you can try doing this solution:

1. Click on the Start menu then type regedit
2. Once the window opens, go to HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionProfileList
3. Create a backup for your registry key (since this process is a bit risky). Select ProfileList then click on File and Export then choose your backup name.
4. From the ProfileList IDs, remove anything with ProfileImagePath in it.
5. Close Regedit then reboot. By this time, the KB3081424 should properly install.

Method Three: Perform A Startup Repair

Another thing you can try to solve the Windows setup in continuous reboot loop problem is to perform a startup repair from a working computer.

1. Ensure that all unnecessary devices are disconnected from your computer as your computer might detect them.
2. If you are connected to a network, you need to disconnect from this as well.
3. On a working computer, download the Windows 10 ISO then you can perform a startup repair.
4. Boot your computer from the Windows 10 DVD.

To change your BIOS option to boot from the Windows 10 DVD, follow these steps:

1. Boot your computer then press the F2 function key to enter setup.

NOTE: You must do this quickly since the BIOS loads rapidly.

2. Once you’re inside the BIOS, navigate to the Boot Configuration screen. On this screen, you’ll be able to change the first device to be loaded.
3. Go to Removable Devices then hit Enter. Removable devices could either be a thumb drive or DVD. Select DVD to put it at the top and be the first boot device.
4. Save your changes by pressing on the F10 function key. A setup confirmation box will appear with a message Save configuration changes and exit now. Select Yes.
5. Exit BIOS by pressing on the ESC key. You should be prompted to boot from the Windows 10 DVD at this point.

If you're not able to execute the aforementioned processes on your own, get help or download and install a powerful system optimizer to assist with the windows continuous reboot loop process and other Windows 10 error messages.