An Easy Guide to Resolving Code 18

Intel’s GPU ARC coming aimed at AMD & Nvidia

This is not the first time that Intel is trying to enter the GPU field but its adventures so far were, well let us agree not so good. All of that is hoping to be changed with the upcoming ARC GPU. The first generation of Arc graphics, code-named Alchemist and previously known as DG2, will support desktop PCs and laptops and is set to arrive in the first quarter of 2022. Alchemist will have hardware-based Ray tracing and AI-driven supersampling. This indicates that GPU is aimed to compete in the Hi-end spectrum and battle side by side with Nvidia and AMD on the market. Alchemist will also pack full DirectX 12 Ultimate support. Intel also released names for the next upcoming future generations of ARC GPUs: Battlemage, Celestial & Druid. More information about ARC products will be released later this year. “Today marks a key moment in the graphics journey we started just a few years ago. The launch of the Intel Arc brand and the reveal of future hardware generations signifies Intel’s deep and continued commitment to gamers and creators everywhere,” Roger Chandler, Intel vice president, and general manager of client graphics products and solutions.

Driver Power State Failure Error in Windows

Driver state power failure error can be linked to three things happening in your computer. Incorrect power settings, driver issues, or incompatible hardware. Sadly when this error happens you only receive a blue screen of death with this message: Blue screen of death driver power state failure

Blue screen of death driver power state failure

Sadly receiving this blue screen does not really explain which of the three cases is the correct one and causing the unwanted issue. That being said, this article will not offer you a direct solution this time, it will be more like a guide on what to check and to do in order to remove this error, reason for this is the nature of the error itself. If your computer is booting properly and you can enter Windows without issues the first thing you can try is going into power options and set it to high performance, if you are on a laptop set high performance both ways, when plugged and when on battery. Power performance settings can reflect on some hardware and can cause mayhem. After setting reboot the computer and see if the error repeats itself. If the error persists go to the device manager and see if there is hardware that has any kind of warning beside it. If there is, update the driver or remove the driver of the device to see if this fixes the issue. If all of the previous two things fail there is another thing you could try. Turn off your computer and disconnect all hardware except the most basic one. Now, this may take a long period of time but boot your computer and then repeat this process but each time add a new piece of hardware to eliminate and find which one is causing the issue. When found try to see if it is repairable through driver updates or get a new device.

How to Fix File System Error 2147219196

If you receive an error message saying, “File System Error 2147219196” when trying to open a picture, access a file or when moving a folder on your Windows 10 computer then read on as this post will help you resolve this error. According to experts, this error started to appear right after the Windows Update v1803 was released. Users who installed the new Windows version faced the same dilemma. This error might be caused by a corrupted disk or it could be due to some broken Windows components or due to file system encryptions. Before you troubleshoot the problem, make sure that you are logged in as an administrator.

Option 1 – Update Windows

The first thing you can do to Resolve File System Error -2147219196 is to update Windows. Since Microsoft is already aware of this issue, they might have already released a fix for this in one of their new updates so make sure to check for any available updates on your computer and have it installed right away.

Tap Win + S to open Search then type “update” in the field and from the search results that appear, click on Windows Update.
After that, it will open Windows Update under Settings and from there click the Check for Updates button and let Windows check for any available updates.
And if there are any updates available, download and install them on your Windows 10 computer.
Restart your PC and check if the error is now fixed or not.

Option 2 – Run CHKDSK to check your disk for errors

When it comes to some issues concerning the hard drive or removable devices, there is a utility in Windows that might help which is called “chkdsk”. This error check utility can help with several issues in the system including File System Error -2147219196.

Tap the Win + S keys to open the Search box.
Then type “command prompt” in the field and from the search results that appear, right-click on Command Prompt and select “Run as administrator”.
After opening an elevated command prompt, copy and paste the following command and hit Enter:

chkdsk /r /f

Now if you are prompted to run CHKDSK after your reboot your PC, just tap Y and reboot your PC.
If CHKDSK is not able to find any errors, tap the Win + E keys and navigate the access window. From there, right-click on the concerned drive and click on Properties.
After opening Properties, click on the tab Tools and then click on the “Check” button under the Error-checking section.
Wait until the process is completed and then restart your computer.
Once your computer has restarted, try accessing the file and check if the error persists.

Option 3 – Disable the File System Encryption

File System Encryption allows you to encrypt drives to protect them from being accessed from another computer. This is the standard practice in various organizations in order to protect their data. However, there are times when the file encryption system caused issues for users in accessing files and throws the File System Error -2147219196 instead which is why you need to temporarily disable it to access your file. To do so, follow the steps below.

Tap the Win + R keys to open the Run dialog box.
Then type “control” in the field to open Control Panel.
From there, navigate to Security and select the BitLocker Drive Encryption option from the list.
After that, make sure that all your drives are not encrypted and if any of them are encrypted, turn off encryption by selecting Turn off BitLocker.
Reboot your computer for the changes to take effect.

Option 4 – Run SFC scan

Tap Win + R to launch Run.
Type in cmd in the field and tap Enter.
After opening Command Prompt, type in sfc /scannow
Restart your computer once the scan is completed.

Fix Error codes 12002-4, 12007-4, 12152-4

If you are trying to install Office but got an error saying, “Something went wrong, Sorry we ran into a problem” with error codes 12002-4, 12007-4, or 12152-4 instead, this indicates that you have a problem with your internet connection. Aside from internet connection issues, the problem could also be due to some programs that block the installation files to be downloaded so when they time out, you get these error codes. There are several options you can try to fix the 12002-4, 12007-4, or 12152-4 error codes. You can try to install Office offline or turn off the proxy server or VPN (if you’re using one). You can also try to temporarily disable your antivirus program or Firewall. Refer to the given potential fixes below to troubleshoot and fix the problem.

Option 1 – Try to install Office offline

The first thing you can do if you encounter the error codes 12002-4, 12007-4, or 12152-4 when installing Office is to download an offline copy of Office especially when you’re certain that your internet connection is slow. Once you’ve downloaded it, install it again. The offline installer will download both the 32 and 64-bit versions of Office. Keep in mind that you must download the correct version.

Option 2 – Disable the Proxy server

The first thing you can do is to try disabling the Proxy server as it might be the reason why you’re getting error 0x80244022 for Windows Updates. To disable the proxy server, refer to the steps below.

Tap the Win + R keys to open the Run dialog box.
Then type “inetcpl.cpl” in the field and hit Enter to pull up the Internet Properties.
After that, go to the Connections tab and select the LAN settings.
From there. Uncheck the “Use a Proxy Server” option for your LAN and then make sure that the “Automatically detect settings” option is checked.
Now click the OK and the Apply buttons.
Restart your PC.

Note: If you are using a third-party proxy service, you have to disable it. In addition, if you are also using a VPN, you can try to disable it as well.

Option 3 – Temporarily disable the Antivirus and Firewall

As mentioned earlier, the downloading of the installation files could be blocked by either the antivirus program or Firewall or it could be both especially when the link seems suspicious. To fix this problem, you have to disable both the antivirus like Windows Defender and the Firewall or any third-party software you might be used temporarily and then download the installation files again. Once the download is completed, make sure to turn on the antivirus program and the Firewall again. On the other hand, you can also try downloading in a different location which also means that you have to try a different network. It could be that the load on the current system is too high which is why it’s not able to offer enough bandwidth to download the installation files of Microsoft Office.

Fix Chrome Error ERR_ICANN_NAME_COLLISION

If you are browsing the internet using the Google Chrome browser in your Windows 10 computer but you suddenly encounter an error message that states, “ERR_ICAN_NAME_COLLISION”, read on as this post will walk you through in fixing the problem. Here’s the full content of the error message:

“The site can’t be reached, This site on the company, organization, or school intranet has the same URL as an external website. Try contacting your system administrator. ERR ICAN NAME COLLISION.”

This kind of error is caused by an error in a private namespace or a random redirection to an incorrect proxy server. There are several ways to fix this error. You can try to check the integrity of the Hosts file or check the proxy. You could also try to use the Registry Editor and apply some tweaks or remove any conflicting browser extensions or flush the DNS cache, as well as run a malware scan.

Option 1 – Try to check the integrity of the Hosts file

To check the integrity of the Hosts file, refer to the following steps:

You have to navigate to this path inside File Explorer: C:/Windows/System32/driversetc
After that, look for a file named “Hosts” and right-click on it, and open it with the Notepad app.
Next, make sure that you write the block URLs in your computer in the list and then save the file.

Note: There are times when you are logged in with administrator credentials and you may receive an error message. In such case, type “notepad” in the Start Search and right-click on Notepad from the search results, and then select the “Run as administrator” option. After that, open the Hosts file and make the necessary changes and save it.

Option 2 – Try to check the Proxy server

There are some users who reported that they’ve fixed the problem after they’ve disabled the use of a proxy server using the built-in way. Follow the steps below to disable the proxy server.

Tap the Win + R keys to open the Run dialog box.
Then type “inetcpl.cpl” in the field and hit Enter to pull up the Internet Properties.
After that, go to the Connections tab and select the LAN settings.
From there. Uncheck the “Use a Proxy Server” option for your LAN and then make sure that the “Automatically detect settings” option is checked.
Now click the OK and the Apply buttons.
Restart your PC.

Note: If you are using a third-party proxy service, you have to disable it.

Option 3 – Try to use the Registry Editor

Before you apply some registry tweaks, make sure that you create a System Restore point. Once you have that covered, follow these steps:

Tap the Win + R keys to open the Run utility and type “Regedit” in the field and tap Enter to open the Registry Editor.
After that, navigate to this registry key: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParametersDataBasePath
Look for the default key and double click on it and make sure that its Value data is set as “C:/Windows/System32/driversetc”.
Now exit the Registry Editor and restart your computer to apply the changes made

Option 4 – Flush the DNS cache

You could also try to flush the DNS cache to fix the “ERR_ICAN_NAME_COLLISION” error. All you have to do is open Command Prompt as an administrator and then execute each one of the following commands sequentially to flush the DNS cache:

ipconfig/release
ipconfig/renew
ipconfig/flushdns

Option 5 – Get rid of any conflicting browser extensions

Open Chrome and press Alt + F keys.
Go to More tools and click Extensions to look for any suspicious browser extensions or toolbars.
Click the Recycle bin and select Remove.
Restart Chrome and press Alt + F keys again.
Proceed to On Startup and mark Open a specific page or set of pages.
To check if the browser hijacker is still active, click Set pages, if it is active, overwrite the URL.

Note: If removing the browser extensions or toolbars didn’t work, you can also try to reset your Google Chrome browser.

Open Google Chrome, then tap the Alt + F keys.
After that, click on Settings.
Next, scroll down until you see the Advanced option, once you see it, click on it.
After clicking the Advanced option, go to the “Restore and clean up option and click on the “Restore settings to their original defaults” option to reset Google Chrome.
Now restart Google Chrome.

Option 6 – Run a malware scan using Windows Defender

It is possible that your computer is infected with malware which could be why you’re getting the “ERR_ICAN_NAME_COLLISION” error. Thus, you need to scan your computer using Windows Defender.

Tap the Win + I keys to open Update & Security.
Then click on the Windows Security option and open Windows Defender Security Center.
Next, click on Virus & threat protection > Run a new advanced scan.
Now make sure that Full Scan is selected from the menu and then click the Scan Now button to get started.

Fixing Windows 10 stuck at “Preparing Security Options”

There are cases when your Windows 10 PC can encounter an issue where it gets stuck and will display a message that says, “Preparing Security Options”. If this is happening to your Windows 10 PC, you won’t be able to use your keyboard or even mouse and your screen will only be stuck on the screen as mentioned above. As your computer is still stuck, you will be left with no choice but to shut it down and restart it. Tap the F11 key as soon as your PC powers on. This will take you to the Advanced Startup options where you can carry out some steps. If it still didn’t work, you have to boot your Windows 10 PC into Safe Mode and then try out the troubleshooting options below.

Option 1 – Try using System Restore

You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.

Tap the Win + R keys to open the Run dialog box.
After that, type in “sysdm.cpl” in the field and tap Enter.
Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

Option 2 – Uninstall the Windows Updates you’ve installed recently

The issue could be caused by Windows Updates so you need to check if it’s indeed the case. The best way you can do so is via Safe Mode.

Boot your PC into Safe Mode and then tap the Win + I keys to open Settings.
After that, click on Update and Security and then select Windows Update from the left side menu column.
Next, select the “View installed update history” option on the right-side column and click on Uninstall Updates which will open a window that will show the list of all the installed updates on your PC.
From there, select the update you want to uninstall and click the Uninstall button located in the lower right corner of the window.

Option 3 – Try disabling the Fast Startup

Boot your PC into Safe Mode.
Then tap the Win + R keys to open the Run dialog box.
Next, type in “control” to open Control Panel.
After that, select Hardware and Sound and click on Power Options.
Select “Choose what the power buttons do” from the left side menu pane and click on Change settings that are currently unavailable.
Afterward, uncheck the “Turn on fast startup (Recommended)” entry and click on Save Changes.
Now restart your PC and check if the problem’s fixed.

Option 4 – Try running both the SFC scan and CHKDSK utility

You can do both SFC and CHKDSK using Safe Mode and Advanced Startup options. For Advanced Startup options, click on the Command Prompt option and proceed with the steps. And if you have booted your computer into Safe Mode, follow these steps:

Tap the Win + X keys or right-click on the Start button and click Command Prompt (admin).
After that, type in this command and tap Enter to run the System File Checker or SFC – “Sfc /scannow”.
Alternatively, you can use this command instead if the previous command didn’t work – “sfc /scannow /offbootdir=c: /offwindir=c:windows”.
Wait until the SFC scan is done with the process and then restart your PC.
Next, run the CHKDSK utility and once it’s done checking your disk for errors and then reboot your PC to save the changes made.

Option 5 – Try resetting Windows 10

You can reset your Windows 10 PC using either the Advanced Startup Options or by booting into Safe Mode.

Tap the Win + I keys and go to Update and Security > Recovery.
Then click on Get Started under the Reset this PC section.
After that, follow the on-screen instructions with how you want to reset your PC and what files and settings you want to revert.
Then it will reset your PC by reinstalling it

Option 6 – Try to rename the SoftwareDistribution folder

In this option, the Command Prompt is supposed to be like the one in option 4. You can use both ways there to open the Command Prompt.

Open an elevated Command Prompt as admin and type in the commands below and tap Enter right after you typed in each one of them
net stop wuauserv
net stop bits
rename c:windowsSoftwareDistribution SoftwareDistribution.bak
net start wuauserv
net start bits

Note: You can also rename the SoftwareDistribution folder to “SoftwareDistribution.bak” or “SoftwareDistribution.old” after you boot your PC into Safe Mode.

Option 7 – Try rebuilding BCD

Rebuilding the BCD can help you in fixing the stuck Windows 10.

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.
Next, select Command Prompt and type in the commands below one by one, and tap Enter right after you do so.
exe /FixMbr
exe /FixBoot
- exe /RebuildBcd

Upcoming Windows features for future

It is no secret that Microsoft is trying to keep Windows relevant and that it is trying to make it as good as possible. A new Windows update will bring some interesting stuff in it which well some like it, some not so much. Among various technical and security updates Microsoft will bring some directly visible to each user.

First

of these features will be File explorer compact mode. This feature is a sort of spacing content in file explorer giving it easier access if you are using a touch screen device. Now, this feature is somewhat strange, and altho I can understand and get behind the logic of this move I am not sure I like it. Lucky for me and others who feel the same this option can be turned off for now.

Second

feature is something I can get behind, improvements for virtual desktops. There is an article on errortools about virtual desktops feature and I really hope you are using it since it is a great feature. Anyway, new update will bring us separate desktop wallpapers for each desktop and we will be able to arrange them in order we like.

Third

thing that I would like to address is animation features. We will have windows slowly fade and resize when opened, minimized, maximized, etc. So far we are unable to tell how this can and will it affect overall system performance. I am sure it will have some impact but hopes are that it will be kept to a minimum. If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.

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.

How to Fix Windows Setup Error 0x80300002

Installing a Windows 10 upgrade is definitely not an easy task since the process is not always smooth sailing and you could encounter some errors when doing so. This isn’t unusual since there are various software configurations and hardware configurations as well as services it depends on in order to properly work. So if any of them malfunctions or becomes corrupted, it will affect the process which will result in errors like the error code 0x80300002. When you encounter this kind of Windows Update error, you will see the following error message on your screen:

“We couldn’t install Windows in the location you choose. Please check your media drive. Here’s more info about what happened: 0x80300002”

You can encounter this kind of error if there is corruption in the partition table of the drive where the installation is in progress. In addition, corruption on the Media device could also cause this problem. So if you encounter this error when running Windows Setup, read on as this post will guide you in fixing it. There are several ways to resolve this issue. The first thing you can do is to verify the compatibility between the BIOS and the installation media. You could also try recreating all the partitions as well as recreating the bootable USB drive. For more detailed information, follow the given options below.

Option 1 – Check if the BIOS is compatible with the installation media

The first thing you can do to fix the error is to check if there are any compatibility issues between the BIOS and the installation media you’re using. This is actually one of the most likely reasons why you’re getting the error since this is a complicated point for the Windows installation process. If the installation media is based on GPT, then your BIOS must be based on UEFI. So if you have your bootable media with the MBR partitioning, you need to set your BIOS to Legacy.

In the Windows Search box, type “command prompt” and from the search results that appear, right-click on Command Prompt and select the “Run as administrator” option.
After that, execute this command: exe /convert /allowfullOS
Now, wait until the process is completed since you can track its process on your screen.
Once it’s done, go to Settings > Update & Security > Advanced Startup options and from there, click on Restart Now. This will restart your computer and give you advanced options.
Next, select Troubleshoot > Advanced Options where you will see further options including System Restore, Startup Repair, Go back to the previous version, Command Prompt, System Image Recovery, and UEFI Firmware Settings.
Now select the “Legacy” option. This will take you to the BIOS. Boot Mode is typically available under Boot > Boot Configuration. Once you’re there, set it to Legacy and then save the changes you’ve made. After that, your computer will restart.

Option 2 – Try recreating a new bootable drive

Insert your USB drive into your PC.
Tap the Win + R keys to open the Run dialog box and type in “cmd” and tap Enter to open the Command Prompt. Alternatively, you can also search for “cmd” in the Cortana search box to open Command Prompt.
Once you’ve opened CMD, type in this command to open the DISPART utility – diskpart
After that, you should see a new black and white window that would say, “DISKPART>”.
Next, type in “list disk” in the command line and tap Enter to see the list of all the Storage devices as well as your hard disk connected to your PC. Here, you have to identify your disk’s number.
Type in this command where “X” is the disk number you have identified and then tap Enter – disk X
Type in this command and hit Enter to clear the table records and all the visible data on the drive – clean
Now you have to recreate a new primary partition of the drive so you’ll have to type in this command and tap Enter right after – create part pri
A new primary partition has been created so you have to select it by typing this command and tapping Enter – select part 1
Now you have to format it to make it visible to normal users by typing – format fs=ntfs quick

Note: If your platform supports the Unified Extensible Firmware Interface or UEFI, replace the “NTFS” with “FAT32” in the command on Step 10.

After that, type in this command and tap Enter after – active
Finally, type this command and hit Enter to exit the utility – exit
After you prepare the image for the operating system, save it to the root of your USB Storage device.

Option 3 – Try to recreate all the partitions

If none of the first two options given above worked, then you can try to recreate all the partitions instead. All you have to do is restart the Windows installation process and wait until you get to the part that says, “Where do you want to install Windows?”. From there, you will see options like delete, format, extend, create new partitions, and many more. Now you have to select the Delete all the partitions options and then use the “New” button to create new partitions. Just make sure that you have one primary partition at least where you can install Windows 10. After that, continue the installation of Windows on the new partition. Keep in mind that when you create a new partition, it also recreates the partition table configuration which means that the chances of getting an error are very unlikely.

How to Fix Remote Computer requires network level authentication Error in Windows 10

A couple of Windows 10 users have reported an error on domain-connected systems when they tried accessing their computer systems remotely. This occurs when the network level authentication or NLA is enabled on the computer. If you are one of these users, you better keep reading as this post will guide you on how you can fix this error. To resolve this issue, there are several workarounds you can try. You can either disable this option directly via properties or you can also modify some registry entries or sub-keys and restart the system. When you encounter this problem, an error message pops up that states:

“The remote computer that you are trying to connect to requires network level authentication (NLA), but your windows domain controller cannot be contacted to perform NLA. If you are an administrator on the remote computer, you can disable NLA by using the options on the Remote tab of the System Properties dialog box.”

Or you could also see this error message instead:

“The remote computer requires Network Level Authentication, which your computer does not support. For assistance, contact your system administrator or technical support.”

Before you proceed in troubleshooting the problem using the options provided below, you need to create a backup for your data or system restore point as well as make a copy of any registry entries you are going to modify.

Option 1 – Disable Network Level Authentication via Properties

The NLA is a useful tool that provides your computer with extra security and helps network administrators in controlling who can log into the system with just a click of a single box. However, there are times when it can become a disadvantage and could prevent you from accessing your system remotely. Thus, you need to disable it using Properties.

Tap the Win + R keys to open the Run dialog box.
After that, type in “sysdm.cpl” and tap Enter to open System Properties.
Next, go to the remote tab and uncheck the checkbox for the “Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)” option.
Now click the Apply button to save the changes made and exit System Properties and then try logging into the remote computer again and see if the problem is fixed or not.

Option 2 – Disable NLA via Registry Editor

Note that you can only use this option if the first one didn’t work for you. Take note that this option will require you to restart your PC completely which could mean some downtime if your computer is running a production server. So make sure to save all your work.

Tap the Win + R keys to open the Run dialog box and then type in “Regedit” in the field and tap Enter to open the Registry Editor.
From there, click on File > Connect Network Registry and input the details of the remote computer and then try to connect.
Navigate to the path below after you’re connected:

HKLM >SYSTEM > CurrentControlSet > Control >Terminal Server > WinStations > RDP-Tcp

After that, change the values given below to “0”
- SecurityLayer
- UserAuthentication
The navigate to PowerShell and execute this command – restart-computer

Option 3 – Disable NLA via PowerShell

PowerShell allows you to tap into the remote computer and once you’ve targeted the machine, you can execute the commands given below to disable NLA.

Tap the Win + S to open Search and then type in “PowerShell” in the field. Right-click on the related result and select the “Run as administrator” option.
After opening PowerShell, execute the command below:

Once in the PowerShell, execute the following command:

$TargetMachine = “Target-Machine-Name” (Get-WmiObject -class “Win32_TSGeneralSetting” -Namespace rootcimv2terminalservices -ComputerName $TargetMachine -Filter “TerminalName=’RDP-tcp'”).SetUserAuthenticationRequired(0) Note: In the command given, the “Target-Machine-Name” is the name of the machine you are targeting.

Option 4 – Use the Group Policy Editor to disable NLA

Another option you can use to disable NLA is via the Group Policy Editor. This is ideal for you if you are blanket disabling. Just take note that the Group Policy Editor is a powerful tool and that if you make some mistakes by changing values you have no clue about, you can render your computer useless so make sure that you create a backup for all the values before you proceed.

Tap the Win + R keys to open the Run dialog box.
Then type in “gpedit.msc” and tap Enter to open the Group Policy Editor.
From there, go to this path – Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security
After that, search for “Require user authentication for remote connections by using Network Level Authentication” and set it to disabled.
Now check if the error is fixed or not.

1 2 3 … 171 Next »