Fixing “The .NET Framework 4.7 is not supported on this operating system” Error in Windows 10

In case you don’t know, the .Net Framework is a programming infrastructure introduced by Microsoft. You will need it to run on lots of services and applications. Note that most of the applications that require the .Net Framework are packed with their installation files which is why it will be installed automatically on your computer when you install an application. However, there are instances when you’ll get an error message saying, “The .NET Framework 4.7 is not supported on this operating system” while trying to install the .NET Framework as a standalone service.

The very reason why this error message appears is stated in the error message itself. Although the .Net Framework is supported on Windows 10, it is not actually compatible with some other Windows 10 versions. So it is most likely that you are seeing this error message because the .Net Framework in your computer is not compatible with the Windows 10 version you are running. Since that’s the case, you need to update Windows 10 to fix the problem.

Updating your Windows 10 computer is the only solution you can try to fix this problem. Thus, it is advised that you check for Windows Updates even if you are now using the latest version of Windows 10. And since the issue is caused by an incompatible operating system version, once you install the exact version of Windows 10 required by the .Net Framework, the problem will be fixed. Simply follow the steps given below to do so.

  • Step 1: Tap the Win + R keys to open the Run dialog box.
  • Step 2: After that, type in “winver” in the field and tap Enter.
  • Step 3: Next, your Windows 10 version should be given in the new window that appears. Take note that the number after the Version which is in the second line is your version number of Windows 10. And that the number must be 1507 or 1709. The first two digits in these numbers are the year while the second two represent the month when the update was released. So if you are running a 1709 version, this means that the Windows 10 version you are using was released in September 2017.
  • Step 4: The next thing you have to do is to make sure that you have the Windows 10 version that’s compatible with the .Net Framework. To verify, you need to click here and click on the System Requirements.

After opening the link, take a look at the Supported Operating System section where it says, “Windows 10 Anniversary Update” and “Windows 10 Creators Update”. Since there are users who are not familiar with the version numbers related to both the Anniversary and Creators updates, refer to the list given below.

  • November Update (1511)
  • Anniversary Update (14393)
  • Creators Update (1703)
  • Fall Creators Update (1709)
  • Spring Creators Update (1803)

As you can see, the Creators Update has version 1703 while the Anniversary Update has version number 14393 so if you are using a version lower than the 14393 version then it’s no wonder you aren’t able to install the .Net Framework 4.7 on your Windows 10 PC. Now all that’s left to do is to update your Windows 10 version and make sure that you will be updating it to the latest version available and then try installing the .Net Framework again.

If you like to learn and find out more about various Windows errors, and how to repair them go to our vast archive or use search to find articles that will explain and help you in solving your issue.
However, if you prefer to do things fast and with automatization then we are proposing to use an automated solution for your issues. The application that we are recommending is Advanced System Repair Pro
Advanced System Repair utilizes multiple tools all in one to give you a quick, simple, reliable, and very thorough diagnosis of your PC. It brings you all the tools you need in one program to clean, fix, protect, optimize and boost your PC!
1-Click Maintenance
All the tools to make it simple and easy! It's like having a professional technician at the click of a mouse.

Junk Cleaner
Keeping your computer free from unnecessary clutter also helps make your computer last longer. Like any other machine, if you keep it clean and take care of it, it will serve you better for longer!

Optimize background apps
Optimize applications background activity with the built-in Application Optimizer feature.

Disk Defrag
With a simple 1-click, Advanced System Repair speeds up your PC by assembling fragmented files on your machine and organizing them more efficiently.

Malware Removal
Finds and removes all types of harmful malware including trojans, worms, bots, adware, spyware, PUPs, and more!

Privacy Cleaner
The all-in-one privacy suite to Clean Your Tracks & Protect Your Privacy! Make your computer safe, secure, and more efficient!

System Tweak/Optimizer
ASR will analyze your complete system and settings to adjust your PC to function at its maximum performance.

Registry Cleaner
Over time, as you install and uninstall applications, the registry can become cluttered with old entries and broken settings which can result in program crashes, and annoying messages and slow the computer down.
Visit our Advanced System Repair Pro Download page to inform yourself about all the benefits of this software and get a free trial copy of it.
advanced system repair pro

Advanced System Repair Pro

One-click automated PC repair solution
ASR logo
With Advanced System Repair Pro you can easily
Replace damaged files
Restore performance
Free disk space
Remove Malware
Protects WEB browser
Remove Viruses
Stop PC freezing
DOWNLOAD
Privacy Policy | Terms of Use | Uinstall
Advanced System Repair Pro is compatible with all versions of Microsoft Windows including Windows 11

Share this article:

You might also like

Fix Update Error 0x800705B3 in Windows
Some Windows users are encountering the 0x800705b3 error code after failing to install a pending update on Windows 10. Most commonly this particular issue is reported to occur with Integrated webcam drivers updates and Bluetooth adapter driver updates. Follow the guide below in order to fix the issue and update your Windows successfully

Running the Windows Update Troubleshooter

The majority of users that were dealing with this issue reported that the issue was fixed after they ran the Windows Update Troubleshooter and applied the recommended fix.
  1. Open a Run dialog box by pressing ⊞ WINDOWS + R. Inside the text box, type ‘ms-settings:troubleshoot’ and press ENTER to open up the Troubleshooting menu. Opening the Troubleshooting tab on Windows 10
  2. Once you’re inside the Troubleshooting tab, move over to the right-hand section of the screen and click on Windows Update (under Get up and Running). Next, from the context menu that just appeared, click on Run the Troubleshooter.
  3. Once you’re inside the Windows Update troubleshooter, wait until the initial scan is complete and see if a viable repair strategy is found.
  4. If the scan has identified a strategy with the potential to fix your ongoing issue, click on Apply this fix and wait until the procedure is complete. Applying the fix Note: Depending on the type of fix that was recommended, you might need to follow an additional set of instructions before the fix will be properly imposed.
  5. After you’ve done this, reboot your computer and wait for the next startup to complete.
  6. Open Windows Update once again and see if the installation of this pending update is now successful.

Installing the pending Update Manually

Whether you’re experiencing this issue with an integrated webcam driver or with anything else, chances are you’ll be able to circumvent the apparition of the 0x800705b3 error by using the Microsoft Update Catalog to find, download and install the pending update manually.
  1. Open your default browser and navigate to the root web page of the Microsoft Update Catalog.
  2. Once you’re inside the Microsoft Update Catalog, use the search function (top-right corner of the screen) to search for the update that is failing.
  3. After the search is completed and you get the list of results, look for an updated driver version that is compatible with your Windows version and CPU architecture.
  4. Once you manage to identify the correct Windows Update, click on the hyperlink associated with the update that you want to install, then click the Download button and wait for the process to complete.
  5. After the download is complete, use File Explorer to navigate to the location where you previously downloaded the update.
  6. When you get to the correct location, right-click on the .inf file and choose Install from the context menu that just appeared. Note: If you have multiple failing updates with the same 0x800705b3, repeat the instructions above with every Windows Update that you’re having trouble installing.
  7. At the end of this operation, reboot your computer and see if the problem is fixed at the next computer startup.

Enabling the Windows Installer Service

The Windows installer service is responsible for installing pending updates that get downloaded by the Windows Update component. If this service is disabled on your configuration, none of the updates waiting to get installed will get completed.
  1. Press ⊞ WINDOWS + R to open up a Run dialog box. Inside the text box, type ‘services.msc’ and press ENTER to open up the Services utility.
  2. Once you’re inside the Services screen, move over to the right-hand tab of the screen, scroll down through the list of services and locate the Windows Installer service. When you find it, right-click on it and choose Properties from the context menu that just appeared.
  3. Once you are inside the Properties screen of the Windows Installer services, access the General tab, click on the Start button to force-start the service. Note: If you can, also change the Startup type to Automatic via the associated drop-down menu. However, depending on your administrator settings, this might not be possible.
  4. Restart your computer and wait for the next startup to complete. Once your PC boots back up, attempt to reinstall the driver that was previously triggering the 0x800705b3 error and see if the issue is now fixed.

Performing a Winsock Reset

In case the 0x800705b3 error is related to some kind of network inconsistency (TCP or IP related), you might see Windows Updates failing due to bad data that forces the Windows to abort the installation of new pending updates. In this case, you should proceed by doing a complete Winsock reset procedure to fix the majority of the socket and temporary data-related issues that might cause this behavior. Several affected users have confirmed that this method was the only thing that allowed them to finally fix the Windows Update issue and install pending updates normally. Here are some step-by-step instructions that will walk you through the process of performing Winsock Reset:
  1. Open up a Run dialog box by pressing ⊞ WINDOWS + R. Inside the text box, type ‘cmd’, then press CTRL + SHIFT + ENTER to open up an elevated Command Prompt. Accessing an elevated CMD prompt Note: When prompted by the UAC (User Account Control) prompt, click Yes to grant admin access.
  2. Inside the elevated CMD prompt, type and taste the following commands in order and press ENTER after each one to effectively reset the TCP and IP data that might be responsible for the apparition of the 0x800705b3 error code:
    nbtstat -R
    nbtstat -RR
    netsh int reset all
    netsh int ip reset
    netsh winsock reset
  3. Once every command above is processed successfully, you can go ahead and close the elevated Command Prompt and reboot your computer.
  4. After the next startup is complete, repeat the installation of the Windows Update that was previously failing and see if the issue is now fixed.

Performing SFC and DISM Scans

If none of the ‘superficial’ causes have worked in your case, you should start considering some type of system corruption that might affect your computer’s ability to complete pending updates that are currently waiting to be installed. In case you find yourself in this particular scenario, you should run a couple of built-in utilities capable of fixing corrupted instances that might be currently affecting the Windows Update component. Our recommendation is to start with a simple System File Checker scan. An SFC scan will cross-check every Windows File against a local archive that maintains healthy copies. In case corrupted instances are found, this utility will swap the corrupted instance with the healthy equivalent.

Performing an SFC scan

Once the SFC scan is complete, reboot your computer and wait for the next startup to complete. After your computer boots back up, initiate a DISM scan. This utility works differently in the sense that it relies on a sub-component of Windows Update to download healthy copies for the corrupted Windows files that need to be replaced. Because of this, it’s important to make sure that you have a reliable Internet connection before initiating this operation.

Doing a DISM scan

After the DISM scan is complete, reboot your computer one final time and see if the issue is fixed once the next startup is complete.
Read More
Software review series: QuickLook
QuickLook app is one of the best options to preview files without opening them in Windows 10. It works similar to the Quick Look feature of macOS. This Microsoft Store app has some really interesting features. It lets you preview images, documents, and media files. Also, just a hotkey is needed to preview the content of a file. There is no interface for the app. Only a preview window is visible. You can also expand the preview window to full size. Apart from that, it lets you keep the preview window on top of the other opened applications. For image files, it also provides the EXIF data. After installing this app, just select some file that you want to preview, and press the Spacebar key. That’s it! The preview window will open immediately to view the file content. If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.
Read More
Your computer is running low on resources
Signing in to a computer that runs a Windows 10 version OS is usually fast and straightforward. However, there are instances when signing in takes too long especially if there are a lot of programs in the Startup. So if many things are loading as soon as you log into your computer, it will slow down the sign-in process. Aside from programs in Startup, it is also possible that there are too many users that are logged in to the account. In such a case, you will most likely encounter an error that says, “Your computer is running low on resources, so no new users can sign in. Please use an account that has already been signed in”. If you’ve encountered such an error when you try to log into your computer, read on as this post will be guiding you on how you can fix it. Each time a user signs in to Windows 10, it will allocate resources in order to work smoothly. But, in many cases, the system is running low on resources which is why this error pops up and blocks a sign-in of a new user. To fix it, you can try to log out the existing users, or perform a Cold Boot, as well as run both the DISM tool and System File Checker scan.

Option 1 - Try to logout existing users

The first thing you can do is to log out the existing users. If you have a shared Windows 10 computer, you have to check if someone hasn’t logged out. It could be that some background task or there is an existing program that is still running under that account. So you have to make sure to ask the same user to log out in case there is some unsaved work. On the other hand, if that user is not around, then you reboot the computer right away.

Option 2 - Try Performing a Cold Boot

You could also try to perform a Cold Boot to fix the problem. A Cold Boot is a process that makes sure that the Windows 10 Kernel shuts down properly and releases all the resources held by any account. To perform a Cold Boot, just press and hold the physical power button on your CPU until it goes off. After that, boot your computer regularly and see if you can now log into your account without any error.

Option 3 - Try to run a System File Checker scan

System File Checker is a built-in command utility in Windows 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 you’re getting the error when you log into your computer. To run the SFC command, follow the steps given below.
  • Boot your computer into the Advanced Recovery mode and from there open Command Prompt.
  • 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 4 - run the dism tool

You might also want to run the DISM tool. This tool is known to repair potentially corrupted files in your system as having them could also system issues like the “Your computer is running low on resources, so no new users can sign in” error. To repair these corrupted system files, you can run the DISM commands:
  • Go to the Advanced Recovery mode and select Command Prompt.
  • After that, input each one of the commands listed below sequentially to execute them:
    • Dism /Online /Cleanup-Image /CheckHealth
    • Dism /Online /Cleanup-Image /ScanHealth
    • Dism /Online /Cleanup-Image /RestoreHealth
  • Once you’ve executed the commands given above, restart your computer and check if the problem is now fixed.
Read More
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:

  1. Download and install the Network License Manager for Windows:
  2. Open LMTools and access the System Settings tab. Make a note of the "hostname" and "ethernet address" of the license server.
  3. Generate a Network License File in Autodesk Account.
  4. On the Service/License tab, select Configuration Using Services and LMTOOLS ignores license file path environment variables.
  5. On the Config Services tab, enter a name for the new service in the Service Name field.
  6. 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.”
  7. Make sure the "Start Server at Power Up" and the "Use Services" boxes are checked. Then click Save Services.
  8. On the Start/Stop/Reread tab, click Start Server.
  9. On the Server Status tab, click Perform Status Enquiry.
  10. 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
  1. 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.
  2. 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.
  3. 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.
  1. Create /usr/local/flexnetserver/licenses directory for network license file location
sudo mkdir /usr/local/flexnetserver/licenses
  1. Find the license server Host Name and Host ID.
  2. 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.
  1. Create a debug.log file in the /usr/local/flexnetserver/ directory using the following command:
touch debug.log
  1. 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
  1. To obtain license server status enquiry:
/usr/local/flexnetserver/lmutil lmstat -a -c /usr/local/flexnetserver/licenses/adsk_license.lic
  1. To stop the license server:
/usr/local/flexnetserver/lmutil lmdown -q -force
  • A​​lternatively, 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
To configure the license manager use the following steps:
  1. 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.
  2. 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.
  3. 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"
  1. 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.
  1. To start the Network License Server
    • /opt/flexnetserver/lmgrd -c /opt/flexnetserver/licenses/adsk_license.lic -l /opt/flexnetserver/server_log.log
  2. To obtain license server status enquiry
    • /opt/flexnetserver/lmutil lmstat -a -c /opt/flexnetserver/licenses/adsk_license.lic
  3. 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)
  4. 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
  1. 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.

  1. Type regedit in the Windows Search box and hit Enter key.
  2. Select the following registry key
  • [HKEY_CURRENT_USER\SOFTWARE\FLEXlm License Manager]
  1. As the key is selected, in right panel ADSKFLEX_LICENSE_FILE will be visible.
  2. Right click on the key and delete it.

Specify the license server in ADSKFLEX_LICENSE_FILE system variable 

  1. Go to Start > Control Panel > System and Security > System.
  2. Select Advanced system settings.
  3. On the System Properties dialog, click Environment Variables.
  4. Under System Variables, click New.
  5. 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:

  1. Go to Start > Control Panel > System and Security > System.
  2. Select Advanced system settings.
  3. On the System Properties dialog, click Environment Variables.
  4. Under System Variables, click New.
  5. Enter FLEXLM_TIMEOUT for the variable name and 5000000 for the variable value.
  6. 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:

  1. Open a Terminal window
  2. Type open ~ (Mac) or nautilus ~ (Linux) to open $HOME folder
  3. Drag and drop flexlmrc.txt file from Desktop to the home folder.
  4. 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:
  1. Click the Start menu and type cmd.
  2. Right-click on the Command prompt and choose "Run As Administrator."
  3. 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.
  1. Open Registry Editor (Start > type regedit > ENTER).
  2. Navigate to HKEY_CURRENT_USER\Software\FLEXlm License Manager.
  3. On the right-side, verify of the ADSKFLEX_LICENSE_FILE key exists. If yes, remove it (right-click > Delete).
  4. Run the software again.
  5. Select Multi-user in the Let's Get Started screen.
  6. Follow the steps to connect to your license server.
Read More
Recover or set a BIOS or UEFI Password
If you have been using Windows for quite some time now then you’re probably aware of the BIOS or UEFI password. This password lock is the one that ensures you enter the set password even before your Windows PC boots up. However, there’s just one downside with the BIOS or UEFI password – there is no recovery option, unlike your Microsoft account. Worry not though for this post will guide you on how you can set or recover a BIOS or UEFI password on your Windows computer. The BIOS or UEFI passwords are stored at the hardware level which means that unless the OEM wants or has configured a way to recover the password, it is pretty much impossible to reset it. There are times when they are so strict that the only way to get through it by contacting customer care. Note that any Windows computer with this lock can’t be unlocked by trying to reinstall Windows. In this post, you’re going to have to remove the CMOS battery temporarily, clear unknown BIOS/UEFI passwords using the bios-PW website as well as call customer care. For more details, refer to the options provided below.

Option 1 – Remove the CMOS battery temporarily

In case you didn’t know, every motherboard comes with a CMOS battery which helps the computer system to keep the clock ticking and in making sure that the BIOS settings are not lost when the computer is powered down. Every time a computer is turned on, the CMOS battery ensures that the information is available for the computer to boot up. So when you remove the CMOS battery temporarily, say about 30 seconds or a minute, the settings will be lost. There are some motherboards that are built-in ways that when you remove the battery for long, it will reset everything including the password for the BIOS or UEFI.

Option 2 – Clear the unknown BIOS or UEFI passwords using a bios-PW website

If the first option didn’t work, you can try using this BIOS Password website at http://bios-pw.org/ to clear the password.
  • When prompted by the BIOS, enter the wrong password a couple of times as doing so will lock you out of the system.
  • After that, you will see a new number or code on the screen which will include a message about System Disabled [XXXXX] Service TAG [YYYYY].
  • Next, open the BIOS Password website and enter the XXXXX code in it and make sure to tap the Shift + Enter keys or just enter.
  • Now it will open multiple unlock keys which you can use to clear out the BIOS or UEFI lock on your Windows PC.

Option 3 – Call the customer care

If the second option still didn’t work, you have to call customer care and follow their suggestions for they will walk you through fixing the problem using the service tag or might suggest that you visit a service center to make things easier for you. Note: You also have the option to set a BIOS or UEFI password. Although it isn’t recommended, you still can do it if you really want to. Remember that the BIOS or UEFI interface varies from OEM to OEM so you must find something related to either PASSWORD or SECURITY. You will have the following similar options:
  • Supervisor password – it’s the same as the master password that can change important system settings.
  • User password – with this password, any user can change minor settings.
  • Master password – you can use this password for a hard drive or as a general password.
There are several OEMs that offer micro-control where you have to enter the BIOS password. For instance, you’ll have the option to skip for a normal restart, or when you select a boot device while you might have to enter the password for unattended reboots or when your PC is powered on, etc. And if you are here to remove the password, you need to find a remove password option in the same section. You will be prompted to enter the set password once and if it’s correct, it will remove the BIOS password. After that, you have to save and exit the BIOS then restart your computer and check if the settings are properly applied.
Read More
TeamViewer stuck on Initializing Display
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.
Read More
Applications you should remove from Windows
ApplicationsOver time Applications change, some for the better some for worse. Some of them even stop receiving updates and are old and vulnerable. Sometimes standards change and some file types are not used anymore. Software evolves along with technology and that is good. Keeping old and useless applications inside your Windows is not so good. From various exploits to simply taking up space, maybe even slowing down OS it is always wise and good to clean your Windows from unwanted old applications. In this article, we will be mentioning some relics of old and providing you with an explanation of why you should remove them from your system if by any chance you still have them on it.

Silverlight

Silverlight was meant to be a competitor for Adobe Flash, it is a WEB framework that enables rich media content inside your WEB browser. The issue is that it is not developed anymore and today's browsers do not support it. The only browser that actually can support it is internet explorer which itself is not supported and how there is practically 0 content on today's modern WEB that will require Silverlight, it is safe and recommended to remove it.

Adobe Flash

Speaking of Adobe Flash, you should remove it as well. Flash has stopped receiving support as of January 2021 and browsers have dropped support for it and even blocked it due to security issues. However, there still might be some local installation of Flash itself inside Windows along with the old Shockwave player that stopped receiving support in 2019. You should remove them both.

JAVA

Now this one is tricky, by itself JAVA does not present any security issues since browsers do not support it anymore and the desktop version is not really slowing down your computer. This one has simply put just another media runtime that is not used and simply takes up space and resources. However if you have some applications that you do use that rely on it (I can really just think of JAVA Minecraft at this point) leave it of course but in any other case, it is just purely not needed.

Quicktime

While we are at media runtime and stuff that just simply is not needed, Quicktime is one of them. Now this Apple Video player and codec is still pretty developed and active in Apple’s iOS environment, Windows version has not been updated since 2016 and it was discovered that it contains some critical vulnerabilities. Uninstall it and if you need a player that could play MOV files, just use a VLC player that can play them without any separately installed codec.

uTorrent

This one, the same as CCleaner was once a good application, as a matter of fact, it was the best torrenting application. Sadly it has fallen from its grace very low, from getting tons of ads in its interface to findings in 2015 that code of torrent client was packed with a crypto miner that used system resources of an installed computer to mine crypto without user’s awareness. You should uninstall this torrent client if you would like to get your PC back and not provide it for cryptocurrency mining for the company that developed it. Use qBittorrent or TIxati, open-source and free ones that have everything needed for any torrenting needs.

Toolbars and Browser extensions

There are a lot of toolbars for browsers and extensions that are malicious in nature or simply not updated providing security issues. It is very advisable to remove this as soon as possible.

WinRAR

WinRAR has gained its large popularity solely for the reason that you could download it from the official site like shareware and use it forever. The license never expired and you could use it indefinitely. Sadly not much has been improved in the application itself and it is slowly falling out in its range of what it can do. There are better open source and free options today like 7zip, PeaZip, ZIPvare, and more that are working the same as WinRAR if not even better.

Windows and manufacturers Bloatware

Yes, applications that come bundled with Windows and with some laptops that include manufacturers made software for different tasks like its own specific media players, calculators, etc. It is known that these applications are not better than their open-source rivals and there are too many of them including some that you will probably never use. It is the same as buying a new phone bundled with tons of applications that you do not need, did not ask for, and do not use. Delete all of them. Considering Windows there are also some Store application like Candy Crush Saga demo and other are safe to remove if not needed. That’s it, our advice for old and not needed applications so you can keep your PC safe and fast.
Read More
Fix The selected disk is not a fixed MBR disk
Both the DISKPART utility and the Disk Management are useful tools in Windows 10 that manage the disk space allocation, and so on. But these tools are not without errors as you could also encounter some when you run them. Recently, some users reported getting an error that says, “The selected disk is not a fixed MBR disk when trying to use the DISKPART utility”. Here’s the exact message of the error:
“The selected disk is not a fixed MBR disk. The ACTIVE command can only be used on fixed MBR disks.”
This kind of error only occurs when you try to activate a disk partition on a UEFI system partition. However, the command works only if your computer is based on BIOS/MBR. The UEFI method has no concept of the active partition and since you have a UEFI system, the disk type is GPT instead of MBR. To simply put it, your BIOS needs the MBR disk type while the UEFI needs the GPT disk type. To fix the “The selected disk is not a fixed MBR disk when trying to use the DISKPART utility” error, there are various potential fixes you can try. You might have to disable Secure Boot, convert the disk to MBR or fix the Boot Manager. For more instructions, follow the options provided below.

Option 1 – Disable the Secure Boot in the BIOS

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

Option 2 – Try converting the disk to MBR

You can try to change the File System of the drive from GPT to MBR but before you do so, make sure that you create a backup copy of your data to an external drive. Once you have that covered, follow the steps below.
  • Create a bootable Windows 10 media and boot your computer from it.
  • Next, click on the “Repair your computer” option on the first Windows 10 installation setup window.
  • Afterward, select the operating system partition from the given options and click on Next.
  • Now select Command Prompt within the System Recovery options box and execute this command to initiate the Diskpart utility: diskpart
  • Then type either one of these commands to view the list of all the Disk connects or the partitions on those disks formed: list disk or list volume
  • After that, execute another one of these commands depending on the command you previously entered to select the disk or partition you want to select: select disk # or select volume #
  • Now execute this command to clean your drive: clean
  • Finally, execute this last command to convert the selected disk or partition as MBR: Convert MBR
  • Restart your computer and check if the error is fixed.

Option 3 – Try to fix the Boot Manager

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

How to Fix Windows 10 Error Code 0x803f7001

Error Code 0x803f7001 – What is it?

Error code 0x803f7001 occurs when there is a failure to update your Windows operating system to Windows 10. Usually, a message box pops up with the following statement, “Windows is not activated as your previous version of Windows on this device was not activated prior to upgrade to Windows 10.” When this occurs, common symptoms of the error code will manifest themselves:

  • Inability to upgrade your Windows operating system to Windows 10
  • Message box with error code 0x803f7001

Solution

Restoro box imageError Causes

The cause for error code 0x803f7001 varies. Usually, it occurs for two reasons: 1) when during the process of upgrading to Windows 10, no valid Windows license or product key is found for your device or 2) when a user performs a clean installation of Windows 10. During a clean installation, a new license is usually required to allow you to activate your copy of Windows.

Further Information and Manual Repair

There are two main options available to fix error code 0x803f7001. Usually, the use of a valid product key can help users rectify error code 0x803f7001. You may also try an automated tool to access the best solutions.

Method One: Use a Valid Product Key

A product key is a code containing 25 characters that enable users to activate Windows. You will need to enter the product key in the exact order it appears in order to install your Windows operating system. All users will be able to access this code in an email or on a card within the Windows DVD package they receive upon purchasing a version of the Windows operating system.

To solve error code 0x803f7001, complete the following steps.

  • Step one: Click the Start button then select Settings
  • Step two: Select Update and Security then Activation
  • Step three: Click the Change product key
  • Step four: Type in your valid product key. (To do this ensure the 25 characters are accounted for and in the correct order.)

If the issue causing error code 0x803f7001 relates to your product key, then the instructions within method one will rectify the issue. You will be able to install and activate Windows 10. However, if while attempting to update your Windows operating system, the error occurs once more, you will need to follow the instructions in the manual repair below.

You may also consider contacting a Windows repair technician if you are uncertain of your ability to perform the tasks required to fix error code 0x803f7001. This IT professional will be able to use his or her technical knowledge to perform complex manual repair tasks if the need arises.

Method Two: Install an Automated Tool

Automated tools help PC users eliminate common issues such as Windows error codes. To address or rectify error codes like error code 0x8007007b download a powerful automated tool on your machine. This tool enables users to access quick solutions. It also scans for and corrects issues that may result in error codes or poor PC performance.

Read More
1 2 3 162
Logo
Copyright © 2022, ErrorTools. All Rights Reserved
Trademarks: Microsoft Windows logos are registered trademarks of Microsoft. Disclaimer: ErrorTools.com is not affiliated with Microsoft, nor claim direct affiliation.
The information on this page is provided for information purposes only.
DMCA.com Protection Status