NVIDIA Share is not working or responding

Uninstalling the Weather App in Windows

Windows 10 has a pre-installed Weather app that offers the local weather information, forecast, temperature gradient, historical data, multiple locations, and many more. It can be handy especially if you tend to check on the weather. However, if you are one of those users who barely use this app, you have the option to uninstall it from your computer and that’s exactly what we’re going to do in this post. There are several methods to uninstall the Weather app in Windows 10. You can uninstall it via Settings or Start Menu or even using a command in Windows PowerShell. Note that uninstalling the Weather app does not affect the functionality of your Windows 10 computer by any means so you shouldn’t worry about uninstalling it. To get started, follow the instructions provided below.

Option 1 – Uninstall the Weather app through Settings

The first option you can try to uninstall the Weather app is through Settings. It’s a very simple process so you wouldn’t have any trouble following it.

First, click on the Start menu and go to Settings.
From there, select System > Apps & Features.
After that, wait until the list of apps is opened, and then look for the Weather app and click on it.
Next, click on Uninstall in the given menu to uninstall the Weather app from your computer.

Option 2 – Uninstall the Weather app through the Start Menu

Another simple way to uninstall the Weather app is through the Start Menu. It only takes a right click and there are actually two ways to go about this – one is new with the recent feature update of Windows. How? Refer to these steps:

Click on the Start button and type in “weather” and right-click on the Weather app which appears in the list.
Next, click on the Uninstall option. This will uninstall the Weather app.
You can also use the other uninstall option which you can find on the right side of the list that also shows other quick action for the app.

Option 3 – Uninstall the Weather app through a command in Windows PowerShell

Tap the Win + X key combination and click on the “Windows PowerShell (Admin)” option to open PowerShell with admin privileges.
After that, execute the following Remove App package command for the Weather app to uninstall it.

Get-AppxPackage Microsoft.BingWeather | Remove-AppxPackage

Once done, it will remove the Weather app from your computer.

Fix Winload.efi file missing error

The Winload.efi file is an Extensible Firmware Interface or EFI file. EFI files are executable files for the firmware of the computers that are mainly based on UEFI and execute the tasks of loading the files to the bootloader of the computer. They are used for a specific set of tasks such as turning on the computer, installing Windows, restarting the computer or resetting it, and so on. This is why the Winload.efi file is a significant file so if it gets corrupted, lost, or damaged, it would be impossible for the Windows operating system to proceed. Here are some errors you can encounter that are related to the Winload.efi file:

efi is missing
efi cannot be found
efi is missing or contains errors
This program can’t start because winload.efi is missing from your computer
This application requires the file winload.efi, which was not found on this system.
There was a problem starting [path]winload.efi. The specified module could not be found.

In addition, the 0xc0000225 , 0xc00000e and 0xc0000001error codes are also associated with the Winload.efi file. Before you start troubleshooting the problem, you can try to perform System Restore first. This will help undo any changes you’ve made in your computer that might have triggered the Blue Screen error. To perform System Restore, here’s what you have to do:

First, press 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.

If System Restore didn’t help in fixing the Blue Screen error, now’s the time for you to resort to the troubleshooting tips provided below but before you get started, make sure that your create a System Restore point first.

Option 1 – Try rebuilding the Boot Configuration Data (BCD) and repairing MBR

Once you get to the Welcome Screen part, click on Next.
Afterwards, 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.
Once Command Prompt has been pulled up, the following commands to rebuild BCD files and repair MBR. Don’t forget to hit Enter right after you type each command.
- bootrec /repairbcd
- bootrec /osscan
- bootrec /repairmbr
Once the command line is successful in finding out a Windows installation, hit Y to let it boot from the list which will successfully rebuild BCD.
Now type “exit” to close Command Prompt and then restart your computer to successfully apply the changes made.

Option 2 – Disable the Secure Boot in the BIOS

Disabling the Secure Boot in the BIOS settings is definitely recommended to resolve errors related to the Winload.efi file. 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 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 3 – Run System File Checker scan

You might also try running the System File Checker or SFC scan to fix the error. System File Checker is a command utility built into your computer that helps restore corrupted files and missing files. Refer to the following steps to run it:

Hit the Win + R keys to launch Run.
Type in cmd in the field and tap Enter.
After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

Windows Resource Protection did not find any integrity violations.
Windows Resource Protection found corrupt files and successfully repaired them.
Windows Resource Protection found corrupt files but was unable to fix some of them

Reboot your computer.

Option 4 – Disable the Early Launch Anti-Malware Protection

You need to restart your computer in the Start Menu first while holding down the Shift key on your keyboard.
After that, it will restart your computer to Startup Settings.
Now ensure that the 8^th option is labeled as “Disable early launch anti-malware protection.
Then tap the F8 key since the aforementioned option above is listed at number 8. This should launch and load Windows on your PC with the Early Anti-malware protection disabled for that session only when you try to carry out the same task and then check if the error related to the Winload.efi file is now fixed.

How to Manually Fix 0x8004210A Error Code on Your System

Error 0x8004210A - What is it?

0x8004210A is a typical POP3 email error message. This error may sometimes occur when you try to check your Post Office Protocol 3 (POP3) email account. 0x8004210A error code hampers your ability to both send and receive e-mails on your Outlook account. Error 0x8004210A is displayed in any one of the following formats on your PC:

The operation timed out waiting for a response from the receiving (POP) server 0x8004210a Task 'SMTP server name - Sending and Receiving reported error' (0x8004210A): 'The operation timed out waiting for a response from the receiving (POP) server. If you continue to receive this message, contact your server administrator or Internet service provider (ISP).'

Error Causes

Error 0x8004210A occurs due to several reasons. However, some of the most common reasons include:

Wrong port number for the POP incoming server
Your connection to the mail server is too slow
Incoming and outgoing emails are being scanned and stopped by an antivirus installed on your system
The Outlook send and receive job is being blocked by Firewall
You are sending and receiving large series of emails or large email attachments
Registry issues

No matter what the cause of this error is, to resume email communication via Outlook and to ensure your work productivity is not affected, it is recommended that you resolve this 0x8004210A error code on your PC immediately.

Further Information and Manual Repair

To fix error 0x8004210A, here are some of the most efficient and easy manual methods that you can try:

Method 1

If the cause of the error is related to the internet connection then here’s what you need to do. Try freeing up your internet connection by closing any other online activities in progress or downloads being carried on your system.

Method 2

Try to increase your server time-out periods. To do this, go to the Outlook File menu and choose account settings. Now double click on your email account and more settings. Now click advanced and increase your server timeout period to resolve.

Method 3

If you are trying to send or receive large and heavy emails on your Outlook account, the error 0x8004210A may pop up. This happens because when transferring heavy files the email account automatically locks until the task is complete, however, if it takes more time the next Send and Receive job starts while the first one is still not complete. In such an event, the email server then times out and shows you the error. Therefore to resolve, you will have to show patience. Simply wait for the large email to be sent or received before you start sending another email.

Method 4

If the antivirus installed on your system is the reason for the error pop up, then disable it for a while until the operation is complete. Then enable it once the task is performed successfully.

Method 5

Similarly, if the Firewall installed on your system is preventing Outlook from reaching your mail server, then simply disable the Firewall to resolve.

Disable Telemetry & Data Collection in Windows

The Windows 10 Telemetry and Data Collection features are auto-enabled and they collect all sorts of user activity and sends it to Microsoft. Microsoft says that the data collected only enhances the overall user experience and Windows functionality better but the number of data breaches happening across the globe has forced users to be extra cautious about their data privacy. So naturally, from stronger passwords and other services management, it is only logical to turn off Windows data gathering. To do so:

Press ⊞ WINDOWS + R to open the run dialog.
In the Run dialog type: taskschd.msc
Press CTRL + SHIFT + ENTER key combo to open Task Scheduler in admin mode.
On the left pane, navigate to the: Task Scheduler Library > Microsoft > Windows > Customer Experience Improvement Program
At the location, on the middle pane, right-click on the task named Consolidator and select Disable from the context menu...
Repeat the process with all other tasks listed in the middle pane.
Exit Task Scheduler.

How to Resolve Error Code 0x80070643 in Windows 10

Error Code 0x80070643 – What is it?

Error Code 0x80070643 or Windows Update error code affects various versions of the Windows operating system, including Windows 10. Error code 0x80070643 usually occurs due to corruption within the .Net Framework. When this occurs, users will be unable to install updates they have downloaded on their PC.

Solution

Error Causes

Error codes within Windows occur for many reasons including corrupt system files, viruses, and lack of space on your PC. In terms of error code 0x80070643 in Windows 10, the cause usually relates to a problem with the .NET framework or errors within one’s registry.

Further Information and Manual Repair

To solve error code 0x80070643 in Windows 10, users will need to employ various manual repair methods. These methods seek to fix core problems that result in the error being present on your device in the first place. Thus, the methods include the use of the .Net Framework Repair tool, resetting Windows Update components, or running a clean boot.

Note that the instructions provided in this article must be followed correctly, as making changes to your computer via these manual repair methods can result in serious problems if mistakes are made. Consider a Windows repair technician if you are unable to complete the steps mentioned in the manual repair methods below. Note, failure to rectify this error might result in other error messages, such as error code 0xc004fc03

Method One: Run the .Net Framework Repair Tool

As error code 0x80070643 may be triggered by issues related to the .Net Framework on your machine, it’s important that you download the .Net Framework Repair tool. This tool, as the name suggests, helps to repair errors it detects within the setup or updates associated with the framework.

The tool is available on the official Windows site. Download the tool and follow the instructions provided. Once you’ve downloaded the .Net Framework Repair tool, run it and wait until it fixes all problems detected within the framework.

Afterward, reboot your computer and check to see if Windows Update is functioning properly. If the error code reoccurs, proceed to another solution by implementing the second manual repair method listed in this article.

Method Two: Reset Windows Update Components

This method is the most technical of all the methods mentioned in this article. It will require that Windows 10 user access Command Prompt and make modifications to the Windows registry – an area of the operating system which stores important information, settings and other details regarding hardware and programs installed on your machine. Follow the steps carefully and be sure to back up the registry before proceeding with this manual repair method.

Step one: Type Command Prompt in the search box near Start, then select Command Prompt (Admin).

Step two: Select Yes as soon as the User Account Control box appears.

Step three: Stop Windows Update service, the BITS service, and Cryptographic service by typing the following commands:

net stop bits

net stop wuauserv

net stop appidsvc

net stop cryptsvc

Step four: Be sure to press Enter after typing each command.

Step five: Type the following command, then Enter to delete qmgr*.dat files:

Del "%ALLUSERSPROFILE%Application DataMicrosoftNetworkDownloaderqmgr*.dat"

Step six: Press enter after typing the following command:

cd /d %windir%system32

Step seven: Reregister the files for BITS and Windows Update that you stopped in step three. To do this, type the following commands, selecting Enter after each command:

regsvr32.exe atl.dll

regsvr32.exe urlmon.dll

regsvr32.exe mshtml.dll

regsvr32.exe shdocvw.dll

regsvr32.exe browseui.dll

regsvr32.exe jscript.dll

regsvr32.exe vbscript.dll

regsvr32.exe scrrun.dll

regsvr32.exe msxml.dll

regsvr32.exe msxml3.dll

regsvr32.exe msxml6.dll

regsvr32.exe actxprxy.dll

regsvr32.exe softpub.dll

regsvr32.exe wintrust.dll

regsvr32.exe dssenh.dll

regsvr32.exe rsaenh.dll

regsvr32.exe gpkcsp.dll

regsvr32.exe sccbase.dll

regsvr32.exe slbcsp.dll

regsvr32.exe cryptdlg.dll

regsvr32.exe oleaut32.dll

regsvr32.exe ole32.dll

regsvr32.exe shell32.dll

regsvr32.exe initpki.dll

regsvr32.exe wuapi.dll

regsvr32.exe wuaueng.dll

regsvr32.exe wuaueng1.dll

regsvr32.exe wucltui.dll

regsvr32.exe wups.dll

regsvr32.exe wups2.dll

regsvr32.exe wuweb.dll

regsvr32.exe qmgr.dll

regsvr32.exe qmgrprxy.dll

regsvr32.exe wucltux.dll

regsvr32.exe muweb.dll

regsvr32.exe wuwebv.dll

Step eight: Reset Winsock in Command Prompt by typing the following command, then selecting Enter:

netsh winsock reset

Step nine: Configure proxy settings in Windows 10 with the following command, then press Enter:

netsh winhttp reset proxy

Step ten: To restart the BITS, Windows Update, and Cryptographic service, type the following commands, then press Enter:

net start bits

net start wuauserv

net start appidsvc

net start cryptsvc

Step eleven: Install the latest Windows Update Agent.

Step twelve: Restart your machine.

Once you’ve restarted your PC, check Windows Update to verify if the error code is resolved. You should now be able to access the latest updates on your device. However, if a problem has arisen and the error code reoccurs, you will need to proceed with a Clean Boot.

Method Three: Download an Automated Tool

If you wish to always have at your disposal a utility tool to fix these Windows 8 and other related issues when they do arise, download and install a powerful automated tool.

How to Fix 0x80070643 Error Code

What is the Ox80070643 Error Code?

The 0x80070643 error is a Windows Update error. It may appear on your computers due to several reasons. Though this error does not pose any harmful threats to your system it is still advisable to fix it to ensure your system works perfectly and there are no installation issues.

Solution

Error Causes

The error 0x80070643 error code is usually triggered:

When the MSI software update registration fails
.NET framework installation becomes corrupted on your PC

Though it does not cause any serious damages it is advisable to repair this issue as it may hamper your ability to install updates on your PC.

Further Information and Manual Repair

If you experience the error 0x80070643 on your PC, you don’t have to panic. This error is rated as easy to resolve. All you have to do to fix this error is to uninstall and reinstall the .NET Framework. Here is a step by step guide to repairing the error 0x80070643:

First close all the currently running programs on your PC
Then go to the start menu and click on the control panel. After you click on it you will see a Programs option here.
Now click on Programs and then click ‘Programs and Features’
Under the Programs and Features section, you will see lots of programs. Double click on Microsoft .Net Framework 4 Client Profile.
Now as you double click on it a dialog box will open in front of the screen with 2 options Repair .Net Framework 4 Client Profile to its original state and the other option would be Remove.Net Framework 4 Client profile from this computer. Click on the first option that says Repair.
After clicking on the Repair tab, click ‘Next’ and then click ‘Finish’. This shows that the .NET Framework is repaired.
Now to bring the changes into effect, restart your PC and reboot.
After rebooting it, go to the start menu again and type Windows Update in the search box.
Click ‘Windows update’ to check for and install updates.

Follow these steps to resolve the 0x80070643 error code issue immediately. Nonetheless, to avoid the error 0x80070643 from occurring again, it is suggested that you download the Windows Update tool. This helps keep your system updated. By updating the latest vulnerability and performance improvements on your PC, you can ensure your PC works smoothly and is not exposed to such errors and threats.

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.

Microsoft Surface Go 2 review

The new upgraded Surface Laptop Go 2 is the new iteration of the affordable original Surface Laptop Go aimed to offer good performance at a lower price of under $1000. The new version is not anything vastly different from the original but it comes with much-needed upgrades.

The biggest and main upgrade is the CPU, the Surface Laptop Go 2 is packing now Intel Core i5 1135G7, an Intels 11th generation CPU that should increase battery life. The laptop is also coming with an improved WEB camera and the cheapest one comes now with 128GB of storage instead of 64GB. Price went up from $550 to $599 which is not a big increase considering what was upgraded.

The bad news of new models is that sadly they are still packing only 4GB of RAM, that's really not enough for most applications released in 2022 and the screen is having a relatively low resolution of 1536 X 1024.

Microsoft is still offering all the color variations as in its first offering but added as well a new Sage color that is muted green in tint.

When we look at hardware it seems a little weak but for this price, there is not much competition in the field, and after all this line of models is aimed to provide good performance for an affordable price. If you really need something better you will go with a standard Surface or MAC book instead.

The new laptops are available to pre-order at Best Buy and Microsoft’s online store, and they’ll start shipping on June 7.

An Easy Guide to Fixing Internal Error 2503

Internal Error 2503 - What is it?

Internal Error 2503 mostly pops up on Windows 8. It occurs when you try to uninstall or install software on Windows 8. The error code message may vary and displayed in different formats such as:

The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2503. Called RunScript when not marked in progress The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2503. Called Install Finalize when no installation is in progress

Solution

Error Causes

Some of the most common causes for internal error 2503 are:

Permission not granted to access the Windows Installer Folder
Viruses
Problems with Windows Installer

Further Information and Manual Repair

To repair this issue on your PC without any professional assistance, try the DIY methods given below:

Method 1

Internal error 2503 may occur when your account has limited privileges. You don’t have the privilege to use or access the Windows Installer folder. Your inability to access this folder hampers you from successfully install or uninstall the desired program on your PC. To gain access, you need to ensure you have permission.

For this navigate to the C:\windows folder. Here find the installer folder and then right-click and choose properties.
After that click on the security tab and check if the System and Administrator account has Full access permission.
For that make sure the system group option has ‘all’ selected to allow you full permission.

Method 2 - Re-register Windows Installer

Another alternative to resolve internal error 2503 is to re-register Windows Installer.

To do this, go to Start and click Run. Now type ‘msiexec /unreg’ in the Run box and then press enter.
Follow the same steps and now type ‘msiexec /regserver’ in the box and then press enter. This will resolve the issue.

Method 3 - Remove Viruses

If internal error 2503 is triggered by a viral infection on your PC, then it is advisable to download an antivirus and scan your entire system. Viruses are notorious for system failures and pose data security threats. If not removed timely, these malicious programs can damage your PC. To remove all viruses on your system, run an antivirus. An antivirus detects all malicious software programs including viruses, malware, adware, and spyware. Delete all the malicious files found right away. This will help resolve internal error 2503.

Razer unveils their first internal PC hardware

Razer is a well-known brand among PC gamers and users, it started as a peripheral manufacturer focused on keyboards and mouse but after years passed Razer expanded its inventory offerings. It soon started offering headphones and lately has branched into wider product lines like gaming chairs and protection masks. It is not a big surprise that Razer is expanding into other branches of the PC industry. This time, however, it has revealed not one but three new hardware for your PC. Case fans, all in one liquid cooler and power supply. There are not many details about the products themselves but one thing is one hundred percent confirmed, they come with Razer Chroma, all of them, even the fans.

Katana Chroma ATX PSU

Most interesting for me personally is Razers Katana, the power supply unit. It is a modular power supply ranging from 750W to 1200W with the additional option of Titanium rated one with an impressive 1600W of power. Power supply will start shipping in early 2022 and at the time of writing this article no price range has been released.

Razer Hanbo AIO

Hanbo liquid cooler will feature an optimized intake design so it can ensure greater heat transfer and fluid dynamic for improved reliability and silent operation. Radiator comes in 240mm size with two fans and a larger one of 360mm with three fans. The pump will be able to rotate in any direction of full 360 degrees so it can fit in any case. Hanbo will be released in November this year but no pricing has been released so far.

Razer Kunai Chroma case fans

Kunai fans will boast high static pressure performance with lowered noise. They will go as far as 2200rpm for the 120mm version where the 140mm version will go up to 1600rpm. They will come with addressable LEDs and up to eight fans will be able to be connected to Razer’s PWM fan controller that will come with a magnet at the back for easy attachment to any steel part of PC casing. PWM will use Razer’s Synapse software to customize pulse width modulation in order to improve airflow and noise. PWM will be priced at $49.99 in the Razer Store and it is available for preorder. Fans are priced at $44.99 for one 120mm or $129.99 for a three-pack of 120mm. One 140mm will go for $49.99 and a three-pack will be $129.99.

1 2 3 … 171 Next »

NVIDIA Share is not working or responding

Option 1 – Try to update the drivers from the official site of NVIDIA

Option 2 – Try to roll back the driver to the previous version

Option 3 – Try disabling NVIDIA Share

Do You Need Help with Your Device?

Share this article:

You might also like

Option 1 – Uninstall the Weather app through Settings

Option 2 – Uninstall the Weather app through the Start Menu

Option 3 – Uninstall the Weather app through a command in Windows PowerShell

Option 1 – Try rebuilding the Boot Configuration Data (BCD) and repairing MBR

Option 2 – Disable the Secure Boot in the BIOS

Option 3 – Run System File Checker scan

Option 4 – Disable the Early Launch Anti-Malware Protection

Error 0x8004210A - What is it?

Error Causes

Further Information and Manual Repair

Method 1

Method 2

Method 3

Method 4

Method 5

Error Code 0x80070643 – What is it?

Solution

Error Causes

Further Information and Manual Repair

Method One: Run the .Net Framework Repair Tool

Method Two: Reset Windows Update Components

Method Three: Download an Automated Tool

What is the Ox80070643 Error Code?

Solution

Error Causes

Further Information and Manual Repair

Causes of the error:

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:

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

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

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

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

Windows:

Clear license server information from the system registry.

Specify the license server in ADSKFLEX_LICENSE_FILE system variable

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

Mac/Linux:

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

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

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

Internal Error 2503 - What is it?

Solution

Error Causes

Further Information and Manual Repair

Method 1

Method 2 - Re-register Windows Installer

Method 3 - Remove Viruses

Katana Chroma ATX PSU

Razer Hanbo AIO

Razer Kunai Chroma case fans