Fix Microsoft Word Stopped Working in Windows

Delete Downloaded, Failed and Pending Windows Updates in Windows 10

There are instances when instead of fixing problems the Windows Update brings you problems on your Windows 10 computer. You might even see some pending Windows Updates which for some reason, refuse to install no matter what you do. The good thing is you won’t have to deal with those failed and pending updates that are incompletely downloaded to your PC as you can actually delete them. Follow the instructions prepared below to delete the failed and pending Windows Updates.

Step 1: The first thing you have to do is delete all the contents in the Temporary folder

Tap the Win + R keys to open the Run dialog box.
Next, type in “%temp%” in the field and hit Enter or click OK to open the Temporary folder.
From there, select all the folders and files within the Temporary folder and then delete them all.

Note: %temp% is one of the many environment variables in Windows that could open the designated folder by Windows as the Temporary folder which is usually located at C:\Users[username]AppDataLocalTemp.

Step 2: Next, remove the pending.xml file

Go to the C:\Windows WinSxS folder.
Once you’ve opened the folder, look for a file named “pending.xml” file and right-click on it and you can either rename it or delete it.
After that, the Windows Update should delete the pending tasks and build a fresh new update.

Step 3: Delete all the contents of the SoftwareDistribution folder

The Software Distribution folder in the Windows operating system is a folder that can be found in the Windows directory and is used to store files temporarily which might be required to install the Windows Update on your PC. Thus, it is required by the Windows Update and maintained by WUAgent. Aside from that, it also contains all the Windows Update History files and once you delete them, you will most likely lose the Update history. As a result, the next time you run the Windows Update, it may result in a longer detection time.

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, got to the C:\Windows\Software\Distribution folder and get rid of all the folders and files thereby 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.

Step 4: Try resetting the catroot2 folder

You can also try resetting the catroort2 folder as it is known to fix tons of Windows Update issues. Both the Catroot and catroot2 are Windows operating system folders that are required for the Windows update process. So when you run the Windows Update, the catroort2 folders stores the signatures of the Windows Update package and helps it in the installation. It makes use of the “%windir%System32catroot2edb.log” file in the updating process. Afterward, the updates are stored in the SoftwareDistribution folder which is used then by the Automatic Updates in order to execute the updating process. Keep in mind that you must not rename or delete the Catroot folder. Although the Catroot2 folder is recreated automatically by Windows, the Catroot folder isn’t.

Fix THREAD_STUCK_IN_DEVICE_DRIVER 0x000000EA

If a program tried and failed to use the Graphics rendering capabilities of a computer, Windows 10 will most likely throw a Blue Screen error that says, “ THREAD_STUCK_IN_DEVICE_DRIVER ”. 0x000000EA is the Stop code for this particular Blue Screen error and could be caused by a bad display driver or bad video card. Whatever the cause is, here are some suggestions you need to check out to resolve this Blue Screen error.

Option 1 – Try to rollback, update, or disable the Graphics card drivers

Since the THREAD_STUCK_IN_DEVICE_DRIVER Blue Screen error has something to do with Graphics card drivers, you can either roll back, update or disable them depending on your preference in order to resolve the error.

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.

Option 2 – Try removing hardware or drivers that you’ve installed recently

If you have recently installed some hardware or drivers, you might want to disable or remove them since external devices are proven to be one of the factors that trigger Blue Screen errors like THREAD_STUCK_IN_DEVICE_DRIVER. All you have to do is physically disconnect any external devices that are connected to your computer and then check if it fixes the BSOD error or not.

Option 3 – Run System File Checker at boot time

Once you get to the Welcome Screen part, click on Next.
Afterward, click on the Repair your computer option located on the bottom-left part of the window.
Then click on Troubleshoot.
Next, select the Advanced Options and then Command Prompt.
After opening Command Prompt, type the “sfc /scannow” command and hit Enter to run the System File Checker scan.
Wait until the process is completed and type “exit” to close Command Prompt and then restart your computer to successfully apply the changes made.

Option 4 – Try to run the Blue Screen Troubleshooter

As you know, the Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like the THREAD_STUCK_IN_DEVICE_DRIVER error. 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.
After that, 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 5 – Try to manually check the Graphics Card hardware

You might also want to check the physical status of your Graphics card and you can do this by disconnecting the Graphics card or any other external device connected to your computer. Once you’ve removed the external device, check it for any damages. If there’s none, connect it back to your computer and check if the THREAD_STUCK_IN_DEVICE_DRIVER Blue Screen error is fixed or not.

Option 6 – Uninstall any faulty drivers

You can also uninstall any faulty drivers via Device Manager. How? Refer to these steps:

Tap the Win + R keys to launch the Run dialog box.
Then type “devmgmt.msc” in the field and tap Enter to open the Device Manager.
From there, look for any faulty drivers. You can identify them easily as they will be marked with a yellow exclamation point. And then check which entries would not affect the normal functioning of your PC.
Now click on the entries of every faulty driver and click on the Uninstall option.
Once you’ve uninstalled them, restart your computer to allow your computer to reinstall the faulty drivers you’ve just removed.

Fix Printer driver issue in Windows

The printer can stop working for many various reasons, some of them are however tied to the printer driver itself. In this guide, we will address issues and provide you with advice on how to get your printer back in working order in no time. All of that being said let us fix your Printer driver issue.

Check to see if the printer is plugged and that it has toner or colors and paper in the tray
The simplest solutions are the best ones, and most of the time simplest issues are overlooked. To eliminate any basic issues check the printer cable does it has paper in the tray and check the status of toner or colors in it.
Check if Windows troubleshooter will resolve the issue
Bring up settings and choose devices, under devices click on printers and scanners. On the far right top, you have a link to start the troubleshooter, click on it. Windows built-in tools could resolve issues and fix them for you. If by any chance Windows is not able to find or resolve issues move to the next step.
Check if the Device Manager is reporting an error and update the driver
If the hardware is functioning properly then the issue might be in Windows not detecting device or driver malfunction. In any case, the Device Manager will be the one who will report this problem. In order to check to see if the driver is properly working press ⊞ WINDOWS + X to open the hidden start menu. Once it opens, click on Device Manager to open it, If you have a driver device error inside Windows, you should see it immediately when entering the Device Manager, it will have a yellow exclamation mark beside it. Right-click on it and choose update driver.
Reinstall driver
If driver update failed or you already have the latest drivers, reinstalling them could fix the issue since drivers might have corrupted during installation of some update or application. Follow steps from point 3 to get to the driver in Device Manager, then right-click on it but instead of update choose to uninstall. Reboot Windows once the driver is uninstalled and Windows will install a new one automatically. If you do not want to update drivers automatically install the latest driver for your device, then reboot.
Check Windows update
Check to see if the latest Windows update is installed, update your Windows if needed
Fix driver issue with DRIVERFIX
If everything else fails, get DRIVERFIX, a premium solution for your PC issues, and fix driver errors.

Diablo 3 lost connection to the game server

Diablo has changed how action RPG games are made and has placed homework for many developers. Diablo 3 is 3rd continuation in the series and to the joy of many players worldwide it has brought some interesting things in the genre like teaming up with other friends to slay demon hordes together introducing much needed multiplayer element. Sadly sometimes we get the error that Diablo 3 can not connect or that the connection to the game server has been lost. Keep reading and try provided solutions as they are presented to fix this issue and continue gaming.

Battle net fix
Check to see if Battle net or Diablo 3 are fully updated to the latest version, if not, update them and try playing
Antivirus Scan
Run the antivirus scan on your system, the virus can interfere with the network and can cause this issue
Restart your Wi-Fi/Network
Wifi router or network adapter can sometimes experience errors and delays due to lost packets and other hardware issues. Resetting the router or network adapter can solve this issue since on reboot it will fetch new addresses.
Update Network Driver
It is very important to keep all of your drivers updated. Go to device manager and update your network driver to the latest version.
Change the DNS Server
This works most of the time, go to your network properties and open settings for IPv4, change DNS to 8.8.8.8 and put 8.8.4.4 as the alternate. Try running the game now.
Reset Winsock Data
Winsock is a program which describes how the Windows network software contact network services. So, in this case, resetting Winsock data may work for you. Run Command Prompt as administrator. Next, type the command netsh winsock reset > Enter. Restart your PC > launch Diablo 3, and check if the error message “Diablo 3 lost connection to game server” is fixed.
Flush your DNS & Renew your IP
Press Win + R key > in the Run dialog box type CMD > and run Command Prompt as admin. And in the command prompt > type ipconfig /flushdns > hit Enter. Now type the given commands in the command prompt > hit Enter after each
- ipconfig /release
- ipconfig /renew And Exit the command
Disable the Proxy Server
Press Win + R key and in the Run dialog > type inetcpl.cpl > Enter. Connections tab > choose Never dial a connection > and click on LAN settings. Then uncheck the box Use a proxy server for your LAN. But if it is already unchecked then check the box next to Automatically detect settings. > hit OK.
Stop Bandwidth Hogging Applications
Press Ctrl + Shift + Esc > open Task Manager > and right click on the application > choose End task

Network License NotAvailable15.570.0 Autodesk

If when trying to start Autodesk applications you receive a Network license not available error then please keep on reading, this guide is for you:

Causes of the error:

The license on the License Server is invalid.
The port for Autodesk Network License Manager is blocked.
The client computer is configured with incorrect license server information.
The license request is timing out on the client's computer before the license is obtained.

Solutions for the error:

Verify that the Autodesk License Server is setup with the correct license file.

To set up a license server for Windows, perform the following:

Download and install the Network License Manager for Windows:
Open LMTools and access the System Settings tab. Make a note of the "hostname" and "ethernet address" of the license server.
Generate a Network License File in Autodesk Account.
On the Service/License tab, select Configuration Using Services and LMTOOLS ignores license file path environment variables.
On the Config Services tab, enter a name for the new service in the Service Name field.
Fill the following fields, using the Browse buttons:
- Path to the lmgrd.exe - Navigate to this file: C:\Autodesk\Network License Manager.
- Path to the License file - Navigate to the new Autodesk.lic file, typically placed in: C:\Autodesk\Network License Manager\Licenses.
- Path to the Debug Log file: C:\Autodesk\Network License Manager.
- If no file is present, create a TXT file in Notepad and rename it “Debug.log.”
Make sure the "Start Server at Power Up" and the "Use Services" boxes are checked. Then click Save Services.
On the Start/Stop/Reread tab, click Start Server.
On the Server Status tab, click Perform Status Enquiry.
Licenses should display as active.

How to set up the Autodesk Network License Manager on a Mac.

Note: The Autodesk License Server Manager (version 11.16.2.0) is supported only on the following Mac operating systems:

Apple macOS High Sierra 10.13
Apple macOS Sierra 10.12
Apple Mac OS X El Capitan 10.11

Download Autodesk Network License Manager version 11.16.2.0 for Mac
- Download the nlm11.16.2.0_ipv4_ipv6_mac_universal.tar.gz file to the Desktop.
To install the Autodesk Network License Manager:
- Double click on nlm11.16.2.0_ipv4_ipv6_mac_universal.tar.gz to unpack the installer package.
- After unpacking nlm11.16.2.0_ipv4_ipv6_mac_universal.pkg, will be /Downloads/adlm/FLEXnet folder.
- Double click on nlm11.16.2.0_ipv4_ipv6_mac_universal.pkg to start installation and follow the installation wizard.
- The license server will be installed in /usr/local/flexnetserver/ directory.
Change permissions for /usr/local/flexnetserver/ directory to 777

Open Terminal (located in /Applications/Utilities/Terminal) and enter the following command:

sudo chmod -R 777 /usr/local/flexnetserver

Note: Administrator password may be asked. While typing no characters are shown, just type out the password and hit return key.
Note: To start the license server only with elevated permissions (using sudo command), change permissions to 755 instead of 777.

Create /usr/local/flexnetserver/licenses directory for network license file location

sudo mkdir /usr/local/flexnetserver/licenses

Find the license server Host Name and Host ID.
Generate the Network License File in the Autodesk Account
- Once the license file is generated, make sure it has a .lic extension (e.g. adsk_license.lic) and is in a plain text format and place it in /usr/local/flexnetserver/licenses directory

Note: In this article we will refer to adsk_license.lic as network license file name. Feel free to change the actual name of the license file, but make sure to reflect the new name when using the commands below.

Create a debug.log file in the /usr/local/flexnetserver/ directory using the following command:

touch debug.log

To start the Network License Server use the following command:

/usr/local/flexnetserver/lmgrd -c /usr/local/flexnetserver/licenses/adsk_license.lic -l /usr/local/flexnetserver/debug.log

Note: If folder permissions for /usr/local/flexnetserver/ are set to 775, then use sudo command to start the server. For example:

sudo /usr/local/flexnetserver/lmgrd -c /usr/local/flexnetserver/licenses/adsk_license.lic -l /usr/local/flexnetserver/debug.log

To obtain license server status enquiry:

/usr/local/flexnetserver/lmutil lmstat -a -c /usr/local/flexnetserver/licenses/adsk_license.lic

To stop the license server:

/usr/local/flexnetserver/lmutil lmdown -q -force

Alternatively, run ps command to obtain process ids for lmgrd and adskflex and then kill those processes:

ps -ax | grep lmgrd
ps -ax | grep adskflex
kill -9

(provide process ids obtained by previous commands individually)

How to set up the Autodesk Network License Manager on Linux.

Note: The Autodesk License Manager (11.16.2.0) is supported only on the following Linux distros:

Red Hat® Enterprise Linux® 7
Red Hat Enterprise Linux 6
SUSE Linux Enterprise 12
SUSE Linux Enterprise 11

See System Requirements for the Network License Manager

To configure the license manager use the following steps:

Download Autodesk Network License Manager v. 11.16.2 for Linux from this link
- Download the nlm11.16.2.0_ipv4_ipv6_linux64.tar.gz file to your desktop.
To install the Autodesk Network License Manager run following command as root.
- tar –zxvf nlm11.16.2.0_ipv4_ipv6_linux64.tar.gz
- rpm -vhi nlm11.16.2.0_ipv4_ipv6_linux64.rpm
- The license server will be installed in /opt/flexnetserver/ directory.
Find the license server Host Name and Host ID

To obtain the license server system hostid run the following command

/opt/flexnetserver/lmutil lmhostid From the command output note the hostid in quotes, if the system has two active NIC cards, select the first MAC address. lmutil - Copyright (c) 1989-2018 Flexera. All Rights Reserved. The FlexNet host ID of this machine is "000c297949e0"

To obtain the license server system hostname run the following command

/opt/flexnetserver/lmutil lmhostid hostname From the command output note the hostname of the license server. mutil - Copyright (c) 1989-2018 Flexera. All Rights Reserved. The FlexNet host ID of this machine is "HOSTNAME=Centos7.localdomain"

Generate your Network License File in Autodesk Account
- Once the license file is generated, make sure it has .lic extension (e.g. adsk_license.lic) and place it in /opt/flexnetserver/licenses directory. If the directory doesn't exits, create it with this command: sudo mkdir /opt/flexnetserver/licenses

Note: in this article we will refer by adsk_license.lic your network license file name.

To start the Network License Server
- /opt/flexnetserver/lmgrd -c /opt/flexnetserver/licenses/adsk_license.lic -l /opt/flexnetserver/server_log.log
To obtain license server status enquiry
- /opt/flexnetserver/lmutil lmstat -a -c /opt/flexnetserver/licenses/adsk_license.lic
To stop your license server service
- /opt/flexnetserver/lmutil lmdown -q -force
- alternatively you can also run ps command to obtain process ids for lmgrd and adskflex and then kill those processes
  - ps -aw | grep lmgrd
  - ps -aw | grep adskflex
  - kill -9 (provide process ids obtained by previous commands individually)
To start the license server automatically after the system reboot
- Open /etc/rc.d/rc.local script as root and enter license server start up command in it.

touch /var/lock/subsys/local /opt/flexnetserver/lmgrd -c /opt/flexnetserver/licenses/adsk_license.lic -l /opt/flexnetserver/server_log.logNote: To ensure that the script will be executed during boot, run following command as root. chmod +x /etc/rc.d/rc.local

Make sure that all necessary ports are open:

lmgrd.exe needs ports 27000 to 27009.
adskflex.exe needs port 2080.

Note: Errors may occur if the network license file is corrupt or in the case of a combined network license it has incorrectly combined licenses. To learn more about combining licenses, see Combining License Files for Multiple Autodesk Products. Use the License File Parser to verify that the license contains the appropriate products and FLEXnet feature codes and does not display an error

Verify that TCP ports (2080, 27000-27009) used by Autodesk Network License Manager are not blocked by Firewall.

The FLEXlm® based version uses the following incoming ports:

TCP ports 2080 (for the adskflex vendor daemon)
TCP ports 27000 to 27009 (for the lmgrd master daemon, which uses the first open port in the range)

Note: If these port addresses are restricted by a router or firewall software, users on the remote side of the router will not have access to licenses controlled by the Network License Manager.

Verify that the client computer is configured with the correct license server name or IP.

Windows:

Clear license server information from the system registry.

Type regedit in the Windows Search box and hit Enter key.
Select the following registry key

[HKEY_CURRENT_USER\SOFTWARE\FLEXlm License Manager]

As the key is selected, in right panel ADSKFLEX_LICENSE_FILE will be visible.
Right click on the key and delete it.

Specify the license server in ADSKFLEX_LICENSE_FILE system variable

Go to Start > Control Panel > System and Security > System.
Select Advanced system settings.
On the System Properties dialog, click Environment Variables.
Under System Variables, click New.
Enter ADSKFLEX_LICENSE_FILE for the variable name and 2080@SERVER_NAME _OR _IP for the variable value.

Note: the license server information most often is recorded in LICPATH.lic file and can be verified there too. ADSKFLEX_LICENSE_FILE system variable supersedes LICPATH.lic. Thus, setting the system variable is preferable when this error is seen.

If the license server is on a VPN or a remote network set the FLEXLM_TIMEOUT environment variable:

Go to Start > Control Panel > System and Security > System.
Select Advanced system settings.
On the System Properties dialog, click Environment Variables.
Under System Variables, click New.
Enter FLEXLM_TIMEOUT for the variable name and 5000000 for the variable value.
Click OK to save the setting.

Note: if needed the variable value can be increased to 10000000.

Mac/Linux:

Specify the Autodesk Network License server information in $HOME/.flexlmrc file.

Use a text editor to create a flexlmrc.txt file and save it in Plain text format (In TextEdit on Mac: Format - Make Plain Text) on desktop. The file content should look like this, except with the name or IP address of the license server.

ADSKFLEX_LICENSE_FILE=@SERVER_NAME _OR _IP

If the license server is on the same machine as the Autodesk software, use localhost as the license server name. Thus, the content of flexlmrc file could look like this:

ADSKFLEX_LICENSE_FILE=@localhost

Note: On firewall restricted network or when accessing the license server via VPN, need to include TCP port/s (usually 27000 or 2080) into Autodesk License Server service as follows: ADSKFLEX_LICENSE_FILE=2080@SERVER_NAME _OR _IP

Once flexlmrc file is created move it to user's $HOME folder as follows:

Open a Terminal window
Type open ~ (Mac) or nautilus ~ (Linux) to open $HOME folder
Drag and drop flexlmrc.txt file from Desktop to the home folder.
To make the file a configuration file, rename it to .flexlmrc (please note . [DOT] in front of the file name) by running the following command:

mv flexlmrc.txt .flexlmrc (Mac)
mv flexlmrc .flexlmrc (Linux)

Verify that the license server information registered with the product is correct (versions 2020 and later only)

In versions 2020 and later, the license server information is registered with the AdskLicensing service running locally on the workstation. When changing to a new license server, the old server information may still be registered with AdskLicensing and result in the error above, if this is not appropriately updated. See the below steps to solve this:

Click the Start menu and type cmd.
Right-click on the Command prompt and choose "Run As Administrator."
In the Command prompt, run the following command, followed by ENTER:

"C:\Program Files (x86)\Common Files\Autodesk Shared\AdskLicensing\Current\helper\AdskLicensingInstHelper.exe" change -pk PRODKEY -pv VER.0.0.F -lm "" -ls "" -lt""

Note:

Replace PRODKEY with the product key correspondent to your product(s). See Look Up Product Keys for the full list.
Replace VER with the version you are using. E.g. 2020 for AutoCAD 2020.
Repeat this step for each software you need to reset.

Open Registry Editor (Start > type regedit > ENTER).
Navigate to HKEY_CURRENT_USER\Software\FLEXlm License Manager.
On the right-side, verify of the ADSKFLEX_LICENSE_FILE key exists. If yes, remove it (right-click > Delete).
Run the software again.
Select Multi-user in the Let's Get Started screen.
Follow the steps to connect to your license server.

Fix PDC WATCHDOG TIMEOUT BSOD

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.

PrintNightmare returns Microsoft states

A few days ago we celebrated fixing of months-long PrintNightmare vulnerability by Microsoft, sadly a new bug and issue have been found. Firstly discovered Microsoft stated:

A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged file operations. An attacker who successfully exploited this vulnerability could run arbitrary code with SYSTEM privileges. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

A few days ago, Microsoft officially released a patch that was supposed to finally fix it. As you might recall this vulnerability was present for quite some time, Microsoft's solution after a long struggle was to elevate certain privileges to administrator account only and remove user accounts from managing printers. It complicated things a little bit but it was stated payoff was worth it. The new issue now is that on a system that already had accounts created and set, old accounts still can hijack the system, patch issues address only accounts that are created after the fix is administrated, old ones can still do whatever they want. Once again of course Microsoft has stated that until it is again resolved you should again disable the Print Spooler service as a temporary workaround.

Prompted For A Product Key On Windows 10 - How to Fix It

Prompted For A Product Key – What Is It?

Some Windows 7 or Windows 8/8.1 users are having a hard time upgrading to Windows 10 as they are being prompted for a product key. By default, the Windows 10 operating system does not require a product key and users should not be prompted for one, given you upgraded your computer from an activated Windows 7 or Windows 8/8.1 license or from the Windows 10 Preview build. However, there are some users encountering this problem and there are several reasons for this.

Solution

Error Causes

There are a few reasons why some users are being prompted for a product key when upgrading to Windows 10:

Windows 7 or Windows 8/8.1 license is not activated.
You’re upgrading to Windows 10 final release from a preview build.
There are broken operating system files.
Activation servers get overwhelmed due to the high volume of upgrades.
The Windows 10 copy you downloaded does not correspond with the current Windows system you are upgrading from.

Further Information and Manual Repair

Before you can fix this problem, you need to know why you’re being prompted for a product key. Some things you should know about Windows 10 product key activation are the following:

You cannot activate Windows 10 using your Windows 7 or Windows 8/8.1 product key. Windows 10 has a unique product key.
Error codes such as 0x8007232b, 0XC004E003, 0x8007007B, or 0x8007000D might pop up during system upgrade especially when the activation servers get overwhelmed with the high volume of upgrades.
You don’t really need to know your Windows 10 product key.

Now, if ever you’re prompted for a product key when you’re upgrading to Windows 10, you can apply the following methods:

Method One: Give It A Few Days

If you’ve been prompted for a product key upon upgrading to Windows 10, you should click on the “Do this later” option. Wait for a few days then Windows 10 will get activated automatically.

Method Two: Download A Copy of Windows 10 Corresponding Your Current System

One of the reasons Windows users are being prompted for a product key when upgrading to Windows 10 is that they have downloaded a wrong edition of Windows 10 and do not correspond with your current system.

Users of Home Basic, Home Premium, Windows 7 Starter, Windows 8.0 Core, and Windows 8.1 Core should download Windows 10 Home ISO.
Users of Windows 7 Ultimate, Windows 7 Professional, Windows 8.0 Pro, and Windows 8.1 Pro should download Windows 10 Pro ISO.

NOTE: Users of Windows 7 Enterprise, Windows 8.0 Enterprise, and Windows 8.1 Enterprise are not eligible for the free upgrade offer.

Method Three: Ensure Windows Is Activated

If your Windows 7 or Windows 8/8.1 is not genuine or activated, you will get prompted for a product key. You need to make sure first your current system is activated.

Click on Start then right-click Computer. For Windows 8 and up users, you can simply press on Windows key + X then select Choose Properties.
When the Properties window appears, check if the Windows you’re running is activated.

Method Three: Reset License Status

Press on Windows key + X.
Select Command Prompt (Admin).
Once the command prompt window appears, type vbs –rearm then press Enter.
Exit Command Prompt then restart your PC.
Input the product key by following the instructions given.

Method Four: Force Activation

Press on Windows key + X
Select Command Prompt (Admin).
Once the command prompt window appears, type vbs –ato then press Enter.
Exit Command Prompt then restart your PC.

Method Five: Run System File Checker

Another thing you can try doing is to run the system file checker utility to scan if there are any broken operating system files. In doing so, you’ll be able to detect problems that might be preventing the product activation of your Windows 10 upgrade.

Method Six: Contact Microsoft Activation Center

If in case you’ve exhausted all your resources and you are still being prompted for a product key when upgrading to Windows 10, you can try contacting the Microsoft Activation Center for further details. Check here for the appropriate telephone numbers to contact.

Method Seven: Download An Automated Tool

If you still experience the error after doing the methods above, you might want to try a powerful and trusted automated tool to fix the job.

Printer not activated, error code 30

If your printer has been working just fine and you suddenly get an error message saying, Printer not activated, error code 30”, then something is definitely wrong and it’s not good especially if you have lots of things to do. Worry not, as this post will help you resolve the printer issue. Simply follow each one of the given options below carefully.

Option 1 – Try running the Printer Troubleshooter

The first thing you can to resolve the printer issue is running the Printer Troubleshooter. This built-in troubleshooter can detect and automatically fix the problem for you. To use it, follow these steps:

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 – Check if the concerned printer is set as the default one

It could be that the printer you are trying to use is not set as the default printer. This is mostly the case so to fix the issue, you need to set the concerned printer as default. To do that, follow the steps below.

Tap the Win + I keys to open the Settings app.
After opening Settings, select Devices from the menu and then click the Printers and scanners option.
From there, look for the printer you are using among the list of options. After you find it, click on it and select the Manage option.
Now click on the “Set as Default” option to set the printer as default.

Option 3 – Try updating the driver for USB Composite Device

The problem with your printer might also be caused by the USB Composite Device. It could be that the USB Composite Device is acting up. Thus, you need to remove and reinstall it. How? 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.
Now uninstall and remove the printer driver software and reinstall it then refresh.

Option 4 – Try updating all the drivers for your Printer

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. Look for Print queues from the list of drivers displayed and click on it to see all the Printer drivers.
Next, right-click on each one of the drivers and select “Update driver” to update the driver. Do it for all the Printer drivers
After that, select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.
Restart your PC and try printing a document again and see if the “Printer not activated, error code -30” no longer pops up.

Note: You also have the option to go directly to the website of your printer manufacturer and check if there’s a new update – if there is, download it.

Fix Realtek HD audio driver issue

Realtek sound device not playing sound is a common Windows issue. It happens occasionally and luckily it can be solved with a little effort and in a short time period. Today in this article we will explore the most common reasons and solutions for driver malfunction for Realtek inside Windows 10. If you have this particular problem, go from step 1 to the last step since all steps are meant to go from simplest to the most complex. All of that being said let us fix your Realtek driver issue.

Check Speakers or/and Headphones first
The first thing would in any troubleshooting be to check are your speakers turned on or are your headphones connected and the volume or switch on them is set properly. Nothing more embarrassing than spending an hour or so troubleshooting only to find out that issue was in a malfunction of speakers or them not being turned on.
Check the Volume control in Windows
Same as the previous step where you have checked hardware, now it is time to check to see if the volume control is set properly and not by any chance muted or volume is brought all the way down.
Check if the Device Manager is reporting an error and update the driver
If both hardware is functioning properly and volume control in Windows is set correctly then the issue might be in Windows not detecting device or driver malfunction. In any case, the Device Manager will be the one who will report this problem. In order to check to see if the driver is properly working press ⊞ WINDOWS + X to open the hidden start menu. Once it opens, click on Device Manager to open it, If you have a driver device error inside Windows, you should see it immediately when entering the Device Manager, it will have a yellow exclamation mark beside it. Right-click on it and choose update driver.
Reinstall driver
If driver update failed or you already have the latest drivers, reinstalling them could fix the issue since drivers might have corrupted during installation of some update or application. Follow steps from point 3 to get to the driver in Device Manager, then right-click on it but instead of update choose to uninstall. Reboot Windows once the driver is uninstalled and Windows will install a new one.
Check Windows update
Check to see if the latest Windows update is installed, update your Windows if needed
Fix driver issue with DRIVERFIX
If everything else fails, get DRIVERFIX, a premium solution for your PC issues, and fix driver errors.

1 2 3 … 171 Next »