Skip to main content

Microsoft Silverlight update is not installing.(error code 64c)



If your getting the above error means that the microsoft silverlight is not installed correctly or the installation is corrupt. If your getting the above error follow the below steps and create a script or I am pasting a link with the script you can download and continue.

  1. Click Start and type Notepad in the Search box
  2. Double-click on Notepad from the list of results above
  3. Copy and then paste the following text into Notepad.
    reg delete HKLM\Software\Microsoft\Silverlight /f
reg delete HKEY_CLASSES_ROOT\Installer\Products\D7314F9862C648A4DB8BE2A5B47BE100 /f
reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\D7314F9862C648A4DB8BE2A5B47BE100 /f
reg delete HKEY_CLASSES_ROOT\TypeLib\{283C8576-0726-4DBC-9609-3F855162009A} /f
reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\install.exe /f
reg delete HKEY_CLASSES_ROOT\AgControl.AgControl /f
reg delete HKEY_CLASSES_ROOT\AgControl.AgControl.5.1 /f
reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{89F4137D-6C26-4A84-BDB8-2E5A4BB71E00} /f
rmdir /s /q "%ProgramFiles%\Microsoft Silverlight"
rmdir /s /q "%ProgramFiles(x86)%\Microsoft Silverlight"
  4. Click File and Save As and type CleanSilverlight.cmd
  5. In the Save astype box, click All Files (*.*)
  6. In the Save in box, click Desktop, and then click Save
  7. On the File menu, click Exit
  8. Right-click the CleanSilverlight.cmd file on your desktop and click Run as administrator
  9. When the uninstall completes, right-click the CleanSilverlight.cmd file on your desktop and click Run as administrator a second time
  10. Once the uninstall has completed, click the link below to install the latest version of Microsoft Silverlight

    http://www.microsoft.com/getsilverlight/get-started/install/default.aspx
  11. Delete the CleanSilverlight.cmd file from your desktop.

your can also download the script from the below link.

https://www.dropbox.com/s/qzlm24aonqn1ffh/CleanSilverlight.cmd?dl=0


Thanks for reading.

Comments

Post a Comment

Popular posts from this blog

  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

How To Resolve VSS Writer Errors Without Rebooting (VShadow)

Background This article describes how to resolve VSS Writer errors without rebooting Windows. Here are the scenarios in which you'd want to use these instructions: Scenario 1: Failed VSS Writers. There are instances when backups are failing due to an agent's VSS writers being in a failed state, but it is impossible or not desirable to restart the server until at least after business hours. Scenario 2: VSS Writers Not Started There may also be a writer that is not running and needs to be. Running the command  - " vssadmin list writers"  will only show a list of writers that are currently started Scenario 3: Using VShadow for Windows Server 2003 or XP VSS is available in the Volume Shadow Copy Service 7.2 SDK, which you can download from the Windows Download Center . Troubleshooting Troubleshooting Scenario 1: Failed VSS writers Find the failed VSS writers and their associated services, and restart them: 1) Run Command Prompt as Administrator (...
Post a Comment
Read more