Skip to main content

The Features your trying to use is on a network resource which is unavailable

Guys when you are  trying to install or Uninstall any software and your getting the below error which is preventing you from doing your work. Please follow the steps mentioned below and you can complete your task.

When your stuck on this error message please follow the below steps.

1. Press W8K + R and put regedit in Run dialog box to open Registry Editor (if you’re not familiar with Registry Editor, then click here). Click OK.

2. In the Registry Editor window, navigate to following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products
3. Expand Products registry key and you’ll see some long randomly named sub-keys. For each of these sub-keys, in the corresponding right pane, you can use ProductName registry string (REG_SZ) to identify to which program this sub-key belongs. Following that, you’ve to find the correct sub-key for the program with which you’re having issues. Once you spotted correct sub-key, right click on it and select Backup. Save the registry file with .reg extension, in case if is required in future. Then do a right click on same sub-key and select Delete. Click OK in confirmation prompt.

You can now close Registry Editor and re-try to install/uninstall program and issue should be resolved now.

Comments

Post a Comment

Popular posts from this blog

ESM Log size is full - How to clear

                                            ESM log Size is full ---- How to Clear If your getting the below error in event viewer you can follow the below steps and solve it. Generally when we open Dell open manage console, suddenly we see that Hardware log status is showing critical and event logs are filling saying ESM log is full... We need to clear the ESM logs regularly before it reaches 100%. However please follow the below command and procedure before clearing the logs. Open Dell Manage console, go to logs tab. Then select ESM logs, you will see an export option. Export the logs and save it on local drive for future use. Now open command prompt and Runas administrator. Type omconfig system esmlog action=clear Done, ...
Post a Comment
Read more
  PowerShell DSC log amount issue on operating system drive Overview Problem Impact Microsoft Ticket (Workaround) solution References Overview When using PowerShell DSC on a configured system in some (seldom) cases it can lead to log amount issues in a specific folder. The following folder grows (over time) so several GB size holding hundreds and thousands of JSON log files as visible in the following screenshot: Also sometimes it looks like this: Problem The problem is (but must not be) related to DSC configuration issues as far as it could be analyzed. The log folder „Configuration Status“ is filled with sometimes up to 7 Megabyte sized JSON files. This log folder (based on our analysis) is used for sending reports to report server but is not cleaned up automatically. Impact Some PowerShell DSC managed systems need extensive disk space due to log directory grown to 40 Gigabyte plus. This causes an alert in disk space / availability monitoring and could in some cases lead to non w...
Post a Comment
Read more

Vm backup failling with snapshot error (156)An error occurred while saving the snapshot: Failed to quiesce the virtual machine.

  Hi Everyone, I am here back with another issue. If anyone is getting error taking backup snapshot of a virtual machine and getting the below error. Vm backup failling with snapshot error (156)An error occurred while saving the snapshot: Failed to quiesce the virtual machine. Apr 28, 2021 2:22:55 AM - Critical bpbrm (pid=15849) from client XXXXX: FTL - vSphere_freeze: Snapshot task for virtual machine XXX-YYY (/vmmor/vm-341) failed, 0 retries remaining, error type: 263, error message: An error occurred while saving the snapshot: Failed to quiesce the virtual machine.. Apr 28, 2021 2:23:08 AM - Critical bpbrm (pid=15849) from client XXXX: FTL - vfm_freeze: method: VMware_v2, type: FIM, function:...
Post a Comment
Read more