This article features error number Code 1622, commonly known as Microsoft Silverlight Error 1622 described as Error 1622: Microsoft Silverlight has encountered a problem and needs to close. We are sorry for the inconvenience.
About Runtime Code 1622
Runtime Code 1622 happens when Microsoft Silverlight fails or crashes whilst it’s running, hence its name. It doesn’t necessarily mean that the code was corrupt in some way, but just that it did not work during its run-time. This kind of error will appear as an annoying notification on your screen unless handled and corrected. Here are symptoms, causes and ways to troubleshoot the problem.
Definitions (Beta)
Here we list some definitions for the words contained in your error, in an attempt to help you understand your problem. This is a work in progress, so sometimes we might define the word incorrectly, so feel free to skip this section!
- Silverlight — Silverlight is Microsoft’s cross-browser, cross platform plug-in for media experiences and rich interactive applications.
Symptoms of Code 1622 — Microsoft Silverlight Error 1622
Runtime errors happen without warning. The error message can come up the screen anytime Microsoft Silverlight is run. In fact, the error message or some other dialogue box can come up again and again if not addressed early on.
There may be instances of files deletion or new files appearing. Though this symptom is largely due to virus infection, it can be attributed as a symptom for runtime error, as virus infection is one of the causes for runtime error. User may also experience a sudden drop in internet connection speed, yet again, this is not always the case.
(For illustrative purposes only)
Causes of Microsoft Silverlight Error 1622 — Code 1622
During software design, programmers code anticipating the occurrence of errors. However, there are no perfect designs, as errors can be expected even with the best program design. Glitches can happen during runtime if a certain error is not experienced and addressed during design and testing.
Runtime errors are generally caused by incompatible programs running at the same time. It may also occur because of memory problem, a bad graphics driver or virus infection. Whatever the case may be, the problem must be resolved immediately to avoid further problems. Here are ways to remedy the error.
Repair Methods
Runtime errors may be annoying and persistent, but it is not totally hopeless, repairs are available. Here are ways to do it.
If a repair method works for you, please click the upvote button to the left of the answer, this will let other users know which repair method is currently working the best.
Please note: Neither ErrorVault.com nor it’s writers claim responsibility for the results of the actions taken from employing any of the repair methods listed on this page — you complete these steps at your own risk.
Method 1 — Close Conflicting Programs
When you get a runtime error, keep in mind that it is happening due to programs that are conflicting with each other. The first thing you can do to resolve the problem is to stop these conflicting programs.
- Open Task Manager by clicking Ctrl-Alt-Del at the same time. This will let you see the list of programs currently running.
- Go to the Processes tab and stop the programs one by one by highlighting each program and clicking the End Process buttom.
- You will need to observe if the error message will reoccur each time you stop a process.
- Once you get to identify which program is causing the error, you may go ahead with the next troubleshooting step, reinstalling the application.
Method 2 — Update / Reinstall Conflicting Programs
Using Control Panel
- For Windows 7, click the Start Button, then click Control panel, then Uninstall a program
- For Windows 8, click the Start Button, then scroll down and click More Settings, then click Control panel > Uninstall a program.
- For Windows 10, just type Control Panel on the search box and click the result, then click Uninstall a program
- Once inside Programs and Features, click the problem program and click Update or Uninstall.
- If you chose to update, then you will just need to follow the prompt to complete the process, however if you chose to Uninstall, you will follow the prompt to uninstall and then re-download or use the application’s installation disk to reinstall the program.
Using Other Methods
- For Windows 7, you may find the list of all installed programs when you click Start and scroll your mouse over the list that appear on the tab. You may see on that list utility for uninstalling the program. You may go ahead and uninstall using utilities available in this tab.
- For Windows 10, you may click Start, then Settings, then choose Apps.
- Scroll down to see the list of Apps and features installed in your computer.
- Click the Program which is causing the runtime error, then you may choose to uninstall or click Advanced options to reset the application.
Method 3 — Update your Virus protection program or download and install the latest Windows Update
Virus infection causing runtime error on your computer must immediately be prevented, quarantined or deleted. Make sure you update your virus program and run a thorough scan of the computer or, run Windows update so you can get the latest virus definition and fix.
Method 4 — Re-install Runtime Libraries
You might be getting the error because of an update, like the MS Visual C++ package which might not be installed properly or completely. What you can do then is to uninstall the current package and install a fresh copy.
- Uninstall the package by going to Programs and Features, find and highlight the Microsoft Visual C++ Redistributable Package.
- Click Uninstall on top of the list, and when it is done, reboot your computer.
- Download the latest redistributable package from Microsoft then install it.
Method 5 — Run Disk Cleanup
You might also be experiencing runtime error because of a very low free space on your computer.
- You should consider backing up your files and freeing up space on your hard drive
- You can also clear your cache and reboot your computer
- You can also run Disk Cleanup, open your explorer window and right click your main directory (this is usually C: )
- Click Properties and then click Disk Cleanup
Method 6 — Reinstall Your Graphics Driver
If the error is related to a bad graphics driver, then you may do the following:
- Open your Device Manager, locate the graphics driver
- Right click the video card driver then click uninstall, then restart your computer
Method 7 — IE related Runtime Error
If the error you are getting is related to the Internet Explorer, you may do the following:
- Reset your browser.
- For Windows 7, you may click Start, go to Control Panel, then click Internet Options on the left side. Then you can click Advanced tab then click the Reset button.
- For Windows 8 and 10, you may click search and type Internet Options, then go to Advanced tab and click Reset.
- Disable script debugging and error notifications.
- On the same Internet Options window, you may go to Advanced tab and look for Disable script debugging
- Put a check mark on the radio button
- At the same time, uncheck the «Display a Notification about every Script Error» item and then click Apply and OK, then reboot your computer.
If these quick fixes do not work, you can always backup files and run repair reinstall on your computer. However, you can do that later when the solutions listed here did not do the job.
Other languages:
Wie beheben Fehler 1622 (Microsoft Silverlight-Fehler 1622) — Fehler 1622: Microsoft Silverlight hat ein Problem festgestellt und muss geschlossen werden. Wir entschuldigen uns für die Unannehmlichkeiten.
Come fissare Errore 1622 (Errore Microsoft Silverlight 1622) — Errore 1622: Microsoft Silverlight ha riscontrato un problema e deve essere chiuso. Ci scusiamo per l’inconveniente.
Hoe maak je Fout 1622 (Microsoft Silverlight-fout 1622) — Fout 1622: Microsoft Silverlight heeft een probleem ondervonden en moet worden afgesloten. Excuses voor het ongemak.
Comment réparer Erreur 1622 (Erreur Microsoft Silverlight 1622) — Erreur 1622 : Microsoft Silverlight a rencontré un problème et doit fermer. Nous sommes désolés du dérangement.
어떻게 고치는 지 오류 1622 (Microsoft Silverlight 오류 1622) — 오류 1622: Microsoft Silverlight에 문제가 발생해 닫아야 합니다. 불편을 끼쳐드려 죄송합니다.
Como corrigir o Erro 1622 (Erro 1622 do Microsoft Silverlight) — Erro 1622: O Microsoft Silverlight encontrou um problema e precisa fechar. Lamentamos o inconveniente.
Hur man åtgärdar Fel 1622 (Microsoft Silverlight-fel 1622) — Fel 1622: Microsoft Silverlight har stött på ett problem och måste avslutas. Vi är ledsna för besväret.
Как исправить Ошибка 1622 (Ошибка Microsoft Silverlight 1622) — Ошибка 1622: Возникла ошибка в приложении Microsoft Silverlight. Приложение будет закрыто. Приносим свои извинения за неудобства.
Jak naprawić Błąd 1622 (Błąd Microsoft Silverlight 1622) — Błąd 1622: Microsoft Silverlight napotkał problem i musi zostać zamknięty. Przepraszamy za niedogodności.
Cómo arreglar Error 1622 (Error 1622 de Microsoft Silverlight) — Error 1622: Microsoft Silverlight ha detectado un problema y debe cerrarse. Lamentamos las molestias.
About The Author: Phil Hart has been a Microsoft Community Contributor since 2010. With a current point score over 100,000, they’ve contributed more than 3000 answers in the Microsoft Support forums and have created almost 200 new help articles in the Technet Wiki.
Follow Us:
This repair tool can fix common computer problems such as blue screens, crashes and freezes, missing DLL files, as well as repair malware/virus damage and more by replacing damaged and missing system files.
STEP 1:
Click Here to Download and install the Windows repair tool.
STEP 2:
Click on Start Scan and let it analyze your device.
STEP 3:
Click on Repair All to fix all of the issues it detected.
DOWNLOAD NOW
Compatibility
Requirements
1 Ghz CPU, 512 MB RAM, 40 GB HDD
This download offers unlimited scans of your Windows PC for free. Full system repairs start at $19.95.
Article ID: ACX08014EN
Applies To: Windows 10, Windows 8.1, Windows 7, Windows Vista, Windows XP, Windows 2000
Speed Up Tip #84
Upgrade to USB 3.0:
Upgrade your computer to USB 3.0 if you are still using the older USB 1.0 or USB 2.0 connections. You can enjoy a transfer speed ten times faster than in USB 2.0. On top of that, the USB 3.0 standard introduces other improvements such as improved bus utilization and better power management.
Click Here for another way to speed up your Windows PC
- Remove From My Forums
-
Question
-
Hi guys, I’m continually getting a error trying to deploy Roxio suite. Looking at the Appenforce.log file, it appears to be the detction method at fault — Application not discovered, keeps on appearing. My understanding of detection method is — the app installs,
then checks for a file, reg entry etc & if present returns an «installed» status. If it doesn’t find it then «failed» appears. However this is after installation right? Because my application is falling over pretty much straight away, so if for example
I have «c:program filesroxioroxio.exe» as my file in detection method, it needs that file to exist however the installation never gets to the point of even creating the folder. Thanks in advance.+++ Starting Install enforcement for App DT «Roxio Creator Starter 12.1» ApplicationDeliveryType — ScopeId_B9A87E16-34B5-40DB-AC14-34AF2BA9E7F5/DeploymentType_5706bab5-14b7-42b5-97b2-8a9afa3eb170, Revision — 25, ContentPath — C:Windowsccmcachet, Execution
Context — System AppEnforce 7/2/2012 3:59:18 PM 3912 (0x0F48)
A user is logged on to the system. AppEnforce 7/2/2012 3:59:18 PM 3912 (0x0F48)
Performing detection of app deployment type Roxio Creator Starter 12.1(ScopeId_B9A87E16-34B5-40DB-AC14-34AF2BA9E7F5/DeploymentType_5706bab5-14b7-42b5-97b2-8a9afa3eb170, revision 25) for system. AppEnforce 7/2/2012
3:59:18 PM 3912 (0x0F48)
+++ Application not discovered. [AppDT Id: ScopeId_B9A87E16-34B5-40DB-AC14-34AF2BA9E7F5/DeploymentType_5706bab5-14b7-42b5-97b2-8a9afa3eb170, Revision: 25] AppEnforce 7/2/2012 3:59:18 PM 3912 (0x0F48)
App enforcement environment:
Context: Machine
Command line: «setup.exe» /qn
Allow user interaction: No
UI mode: 1
User token: null
Session Id: 1
Content path: C:Windowsccmcachet
Working directory: AppEnforce 7/2/2012 3:59:18 PM 3912 (0x0F48)
Prepared working directory: C:Windowsccmcachet AppEnforce 7/2/2012 3:59:18 PM 3912 (0x0F48)
Prepared command line: «C:Windowsccmcachetsetup.exe» /qn AppEnforce 7/2/2012 3:59:18 PM 3912 (0x0F48)
Executing Command line: «C:Windowsccmcachetsetup.exe» /qn with user context AppEnforce 7/2/2012 3:59:18 PM 3912 (0x0F48)
Working directory C:Windowsccmcachet AppEnforce 7/2/2012 3:59:18 PM 3912 (0x0F48)
Post install behavior is BasedOnExitCode AppEnforce 7/2/2012 3:59:18 PM 3912 (0x0F48)
Waiting for process 3076 to finish. Timeout = 120 minutes. AppEnforce 7/2/2012 3:59:18 PM 3912 (0x0F48)
Process 3076 terminated with exitcode: 1622 AppEnforce 7/2/2012 3:59:20 PM 3912 (0x0F48)
Looking for exit code 1622 in exit codes table… AppEnforce 7/2/2012 3:59:20 PM 3912 (0x0F48)
Unmatched exit code (1622) is considered an execution failure. AppEnforce 7/2/2012 3:59:20 PM 3912 (0x0F48)
++++++ App enforcement completed (2 seconds) for App DT «Roxio Creator Starter 12.1» [ScopeId_B9A87E16-34B5-40DB-AC14-34AF2BA9E7F5/DeploymentType_5706bab5-14b7-42b5-97b2-8a9afa3eb170], Revision: 25, User SID: ] ++++++ AppEnforce
7/2/2012 3:59:20 PM 3912 (0x0F48)
Answers
-
Since error 1622 is being returned, it appears that the Setup.exe is calling a MSI package to complete the installation (your ProcMon results support this as well). I think the related MSI log would be the best way to determine the root cause of the
failure.MSI Logging can be enabled following the steps in this KB article:
http://support.microsoft.com/kb/2545723If it is the location of the setup log which is causing the issue, there might be an argument which you can pass via the command line to redirect the log to a different location. I know that MSIExec.exe definitely supports changing the log location,
but the Setup.exe binary you’re using may or may not allow the passing of arguments to the MSI portion of the setup sequence.-
Marked as answer by
Monday, July 9, 2012 8:16 AM
-
Marked as answer by
Номер ошибки: | Ошибка 1622 | |
Название ошибки: | Microsoft Silverlight Error 1622 | |
Описание ошибки: | Ошибка 1622: Возникла ошибка в приложении Microsoft Silverlight. Приложение будет закрыто. Приносим извинения за неудобства. | |
Разработчик: | Microsoft Corporation | |
Программное обеспечение: | Microsoft Silverlight | |
Относится к: | Windows XP, Vista, 7, 8, 10, 11 |
Сводка «Microsoft Silverlight Error 1622
«Microsoft Silverlight Error 1622» также считается ошибкой во время выполнения (ошибкой). Разработчики программного обеспечения пытаются обеспечить, чтобы программное обеспечение было свободным от этих сбоев, пока оно не будет публично выпущено. К сожалению, инженеры являются людьми и часто могут делать ошибки во время тестирования, отсутствует ошибка 1622.
Ошибка 1622, рассматриваемая как «Microsoft Silverlight Error 1622», может возникнуть пользователями Microsoft Silverlight в результате нормального использования программы. Таким образом, конечные пользователи предупреждают поставщиков о наличии ошибок 1622 проблем, предоставляя информацию разработчику. Затем Microsoft Corporation исправит ошибки и подготовит файл обновления для загрузки. Если есть запрос на обновление Microsoft Silverlight, это обычно обходной путь для устранения проблем, таких как ошибка 1622 и другие ошибки.
Что на самом деле вызывает ошибку времени выполнения 1622?
Вполне вероятно, что при загрузке Microsoft Silverlight вы столкнетесь с «Microsoft Silverlight Error 1622». Проанализируем некоторые из наиболее распространенных причин ошибок ошибки 1622 во время выполнения:
Ошибка 1622 Crash — Ошибка 1622 является хорошо известной, которая происходит, когда неправильная строка кода компилируется в исходный код программы. Эти ошибки обычно возникают, когда входы Microsoft Silverlight не могут быть правильно обработаны, или они смущены тем, что должно быть выведено.
Утечка памяти «Microsoft Silverlight Error 1622» — этот тип утечки памяти приводит к тому, что Microsoft Silverlight продолжает использовать растущие объемы памяти, снижая общую производительность системы. Возможные причины из-за отказа Microsoft Corporation девыделения памяти в программе или когда плохой код выполняет «бесконечный цикл».
Ошибка 1622 Logic Error — логическая ошибка возникает, когда Microsoft Silverlight производит неправильный вывод из правильного ввода. Это происходит, когда исходный код Microsoft Corporation вызывает недостаток в обработке информации.
Как правило, такие Microsoft Corporation ошибки возникают из-за повреждённых или отсутствующих файлов Microsoft Silverlight Error 1622, а иногда — в результате заражения вредоносным ПО в настоящем или прошлом, что оказало влияние на Microsoft Silverlight. Как правило, решить проблему можно заменой файла Microsoft Corporation. Кроме того, некоторые ошибки Microsoft Silverlight Error 1622 могут возникать по причине наличия неправильных ссылок на реестр. По этой причине для очистки недействительных записей рекомендуется выполнить сканирование реестра.
Распространенные сообщения об ошибках в Microsoft Silverlight Error 1622
Типичные ошибки Microsoft Silverlight Error 1622, возникающие в Microsoft Silverlight для Windows:
- «Ошибка программного обеспечения Microsoft Silverlight Error 1622. «
- «Недопустимый файл Microsoft Silverlight Error 1622. «
- «Извините за неудобства — Microsoft Silverlight Error 1622 имеет проблему. «
- «Microsoft Silverlight Error 1622 не может быть найден. «
- «Microsoft Silverlight Error 1622 не может быть найден. «
- «Проблема при запуске приложения: Microsoft Silverlight Error 1622. «
- «Microsoft Silverlight Error 1622 не выполняется. «
- «Ошибка Microsoft Silverlight Error 1622. «
- «Неверный путь к программе: Microsoft Silverlight Error 1622. «
Эти сообщения об ошибках Microsoft Corporation могут появляться во время установки программы, в то время как программа, связанная с Microsoft Silverlight Error 1622 (например, Microsoft Silverlight) работает, во время запуска или завершения работы Windows, или даже во время установки операционной системы Windows. Запись ошибок Microsoft Silverlight Error 1622 внутри Microsoft Silverlight имеет решающее значение для обнаружения неисправностей электронной Windows и ретрансляции обратно в Microsoft Corporation для параметров ремонта.
Причины ошибок в файле Microsoft Silverlight Error 1622
Большинство проблем Microsoft Silverlight Error 1622 связаны с отсутствующим или поврежденным Microsoft Silverlight Error 1622, вирусной инфекцией или недействительными записями реестра Windows, связанными с Microsoft Silverlight.
В основном, осложнения Microsoft Silverlight Error 1622 связаны с:
- Недопустимая или поврежденная запись Microsoft Silverlight Error 1622.
- Вредоносные программы заразили Microsoft Silverlight Error 1622, создавая повреждение.
- Вредоносное удаление (или ошибка) Microsoft Silverlight Error 1622 другим приложением (не Microsoft Silverlight).
- Другое программное приложение, конфликтующее с Microsoft Silverlight Error 1622.
- Microsoft Silverlight (Microsoft Silverlight Error 1622) поврежден во время загрузки или установки.
Продукт Solvusoft
Загрузка
WinThruster 2022 — Проверьте свой компьютер на наличие ошибок.
Совместима с Windows 2000, XP, Vista, 7, 8, 10 и 11
Установить необязательные продукты — WinThruster (Solvusoft) | Лицензия | Политика защиты личных сведений | Условия | Удаление