I have a number of different sheduled tasks that are set to run some executable files written in VB.Net. When they go to run they almost always get an error saying that the task failed to start and references this error value:
Additional Data: Error Value: 2147942402
How can I fix this?
asked Aug 8, 2012 at 13:15
2
I was getting the same error message. As pointed out in this other answer, it turns out that the error code 2147942402 actually means File Not Found.
I was creating my Scheduled Task programmatically, and it turned out that I had a typo in the path of the executable that I was specifying to run, and it didn’t actually exist. Once I corrected the file path of the exe that the Scheduled Task was set to run then everything worked as expected.
answered Feb 9, 2018 at 22:41
deadlydogdeadlydog
22.2k14 gold badges109 silver badges118 bronze badges
2
I had the same issue when I tried running web pages with IE using windows scheduler.
Follow these steps:
-Right click your task -> properties.
-Click the Settings tab, look for «If the task is already running, then the following rule applies», should be at the bottom of the dialog, and set the DropDownList value to «Stop the existing instance».
-Click the Actions Tab, edit your task, under Program/script choose the FULL PATH of the application running your task (In my case I replaced iexplore.exe with C:Windowswinsxs…iexplore.exe)
Hope this helps you 
answered Apr 26, 2017 at 15:51
I got the same Additional Data: Error Value: 2147942402.
For me the solution that worked was to delete the task and create the new one, the same that was deleted. You can also try to validate the password for user on with the task is running.
answered Feb 4, 2015 at 7:54
Janusz NowakJanusz Nowak
2,5351 gold badge17 silver badges35 bronze badges
1
Changing permissions, different files or locations didn’t work for me.
I had to create a brand new task and disable the old one, and it worked for me. Something must’ve been corrupted with the original task.
answered Aug 20, 2018 at 16:16
EricEric
312 bronze badges
1
I fixed this error by changing «Run whether user is logged on or not» to «Run Only when user is logged on» on the General tab of the task.
You must a valid user on the General tab-> security options-> «When running the task, use the following user account:»
answered Sep 10, 2021 at 16:48
I was getting this error when running a batch file as my scheduled task. My task action pointed to a batch file and executed successfully but reported operational code 2 and the following details.
Task Scheduler successfully completed task...., action "C:WindowsSYSTEM32cmd.exe" with return code 2147942402
I fixed this by changing the final exit code to:
exit 0
Make sure to trap and handle errors in the batch file. If the batch runs successfully then change «exit» to «exit 0». Now the task scheduler result is «The operation completed successfully (0x0)».
answered Aug 2, 2022 at 20:08
I encountered the same issue while executing the command on the remote server. I fixed the issue by including cmd /c in front of the command.
The command for which I was getting error:
<filepath> <command to run>
The fix that solved the issue.
cmd /c <filepath> <command to run>
answered Feb 12 at 3:57
kgangadharkgangadhar
4,7765 gold badges36 silver badges54 bronze badges
Server 2008 R2 (полностью исправлен)
Я пытаюсь запустить запланированное задание для перемещения файлов указанного типа из C: Windows Temp в E: Foo_blah_blah_blah_blah Foo2 и по какой-то причине получаю следующую ошибку:
Планировщику не удалось запустить экземпляр задачи «{fe0f148a-cece-44a0-a4d1-914aaf21daa8}» задачи » Move Temp Files» для пользователя «FOOBOX Administrator». Дополнительные данные: Значение ошибки: 2147942402
Есть идеи, почему это происходит?
Дополнительные детали:
- Задача настроена для запуска от имени учетной записи, обладающей полномочиями для перемещения файла.
- Задача настроена на выполнение независимо от того, вошел ли пользователь в систему или нет. Это терпит неудачу для обоих сценариев — те же самые ошибки.
- Задача настроена на запуск для локальной ОС (Windows Server 2008)
- Команда разбита на две части. Программа / скрипт:
moveДобавить аргументы:C:WindowsTemp*.foo E:Foo_blah_blah_blah_blahFoo2
Если я запускаю эту же команду move C:WindowsTemp*.foo E:Foo_blah_blah_blah_blahFoo2из командной строки Windows, она работает нормально.
Чего мне не хватает?
Ответы:
Как отметил Райан Райс, 2147942402 переводится как «Файл не найден», что является очень подходящим ответом. Попробуйте нажать Win + R, введите «move» и нажмите enter — это интерактивный эквивалент того, что ваша задача не справляется.
Причина в том, что MOVEэто не программа, а встроенная команда в cmd.
Должен быть:
Программа: "cmd.exe"
Аргументы:"/c move C:WindowsTemp*.foo E:Foo_blah_blah_blah_blahFoo2"
Причина в том, что задание настроено на удаление, если не запланировано повторное выполнение. Это настраивается на вкладке «Настройки». Удаление Задачи выполняется во время истечения Триггера, который запускает Задачу. Если время истечения триггера точно совпадает со временем запуска триггера, может (случайно) произойти, если Задание будет удалено за несколько секунд до срабатывания триггера. Это вызывает событие 101 с кодом причины 2147942402. Решение состоит в том, чтобы установить время истечения триггера на 1 мин позже времени начала триггера.
Может быть, это проблема пробелов в строке порядка заказа:
C: Program Files Wireshark Wireshark.exe -i1 -k FAILS
«C: Program Files Wireshark Wireshark.exe» -i1 -k ОК
- Remove From My Forums
-
Question
-
We’re using a physical installation of Windows Server 2019 Standard at a French location. The server is working normally. Task Scheduler is used for a small number of tasks. One of the tasks runs a CMD-file daily. The CMD-file launches ROBOCOPY which creates
log files. The task runs successfully, since the log files are created. However, the «Action completed» event in the Task History always shows a return code of 2147942402.From Google searches of this return code, it translates to «file not found». But that’s not the case here, since the task runs and Robocopy creates its log files.
If I launch the CMD-file inside a VBS wrapper, Robocopy runs, the log files are created, and the return code is 0.
What does the 2147942402 return code really mean? How can it be avoided without resorting to a VBS wrapper?
regards, AndyA
In this post we’ll talk about three popular windows task scheduler error codes, task Scheduler 2147942401, 2147942402, and 2147942403. Those error prevent users from running their scheduled tasks successfully. If you’re using windows task scheduler often, chances are you’ve come across one or two of these codes. We’ll take a look at all the three error codes separately so that you can fully understand them. Let’s take a look at them right away.
How To Fix Task Scheduler 2147942401, 2147942402 and 2147942403
Task Scheduler 2147942401
When converted to hex code, task scheduler 2147942401 is the same as 0x80070001. This error code is confusing also because the task will be marked as ‘successfully completed’ but with the code 0x80070001. The error code indicate ‘illegal function’
Possible causes
The main cause is when the ‘start in’ for the configured action isn’t filled out.
How to fix it
In order to fill this you should open your schedule task and then right-click to open properties window. Navigate to actions tab and then click edit. When you open it you’ll realize it’s not filled and you need to fill in the path to your batch file. Once you filled that the problem will definitely be solved. This is the best way to fix task scheduler error code 2147942401 which is also the same as 0x80070001.
Task Scheduler 2147942402
2147942402 is the same as 0x80070002 when you convert to hex, it means file not found.
Possible cause
It might be possible there is an error when typing the path to the file, so try checking the file path before applying any fix. Some users have reported making a typo in the file path and fixing it has solved the problem.
Another reason that causes this problem is that you’ve set the task to be deleted if it’s not going to be scheduled again. And hence when you try to run the task again the path will not be found since the task has been deleted. In order to avoid this you need to set expiration time of the trigger at least 1 min ahead of the starting time of the trigger.
How to fix the problem
The fix is almost similar to 2147942403 as mentioned below.
- Right click on the task and click on properties.
- Hit the settings tab and check the last option that says ‘if the task is already running
- Then the following rule applies’ and from the drop down menu you should set as ‘stop the existing instance’.
Second fix
Another way to fix this is to just recreate the schedule task again. Since this error is generated due “folder not found”, recreating the task will create a new folder if the previous one is missing. Even if the folder for the failed task exists, delete it and create a new one.
These are the two effective ways to get rid of this error code.
Task Scheduler 2147942403
You should understand that 2147942403 is the same 0x80070003 in hex value and it means that system is unable to find the specified path. The path that’s saved in task scheduler folder couldn’t be found and hence you receive the message ‘ERROR-PATH NOT FOUND’ which means the system couldn’t locate the path to the given task.
Possible fixes
- Open windows task scheduler; control panel > administrative tools > Task scheduler,
- You should Delete SmartFTP task folder that’s located in task scheduler
- Restart the SmartFTP.
Most of the time the problem will be solved by applying this fix.
Second fix
Another fix is by changing task scheduler settings;
Open task scheduler > click on scheduled job properties > click on settings, There are options listed and you need to take a look at the one that says, ‘if the task is already running, the following rule applies’, in the drop-down options you should select ‘stop the existing instance’, Click save and then exit the window. Go back now and check to see whether your task is running or not. Following the two methods will help you fix task scheduler error 2147942403. Let’s now move to the next error code.
Conclusions:
We’ve now reached the end of the article and if you have any other suggestions that have worked for you regarding these three error codes namely: 2147942403, 2147942402, and 2147942401. Please drop a comment for our readers to learn how to fix the problem. Let us know if the fixes shared here have worked for you or not.
Содержание
- Что вызывает ошибку запланированного задания 2147942402?
- Windows 10 filesystem error (-2144927436) when opening uwp apps and no access to start menu
- Replies (6)
- Ошибка 2147942402 windows 10
- Общие обсуждения
- Ошибка 2147942402 windows 10
- Общие обсуждения
Server 2008 R2 (полностью исправлен)
Я пытаюсь запустить запланированное задание для перемещения файлов указанного типа из C: Windows Temp в E: Foo_blah_blah_blah_blah Foo2 и по какой-то причине получаю следующую ошибку:
Планировщику не удалось запустить экземпляр задачи «» задачи « Move Temp Files» для пользователя «FOOBOX Administrator». Дополнительные данные: Значение ошибки: 2147942402
Есть идеи, почему это происходит?
- Задача настроена для запуска от имени учетной записи, обладающей полномочиями для перемещения файла.
- Задача настроена на выполнение независимо от того, вошел ли пользователь в систему или нет. Это терпит неудачу для обоих сценариев — те же самые ошибки.
- Задача настроена на запуск для локальной ОС (Windows Server 2008)
- Команда разбита на две части. Программа / скрипт: move Добавить аргументы: C:WindowsTemp*.foo E:Foo_blah_blah_blah_blahFoo2
Если я запускаю эту же команду move C:WindowsTemp*.foo E:Foo_blah_blah_blah_blahFoo2 из командной строки Windows, она работает нормально.
Чего мне не хватает?
Как отметил Райан Райс, 2147942402 переводится как «Файл не найден», что является очень подходящим ответом. Попробуйте нажать Win + R, введите «move» и нажмите enter — это интерактивный эквивалент того, что ваша задача не справляется.
Причина в том, что MOVE это не программа, а встроенная команда в cmd .
Программа: «cmd.exe»
Аргументы: «/c move C:WindowsTemp*.foo E:Foo_blah_blah_blah_blahFoo2»
Причина в том, что задание настроено на удаление, если не запланировано повторное выполнение. Это настраивается на вкладке «Настройки». Удаление Задачи выполняется во время истечения Триггера, который запускает Задачу. Если время истечения триггера точно совпадает со временем запуска триггера, может (случайно) произойти, если Задание будет удалено за несколько секунд до срабатывания триггера. Это вызывает событие 101 с кодом причины 2147942402. Решение состоит в том, чтобы установить время истечения триггера на 1 мин позже времени начала триггера.
Windows 10 filesystem error (-2144927436) when opening uwp apps and no access to start menu
Hi Microsoft Community,
I am running Windows 10.0.19041 and experiencing an issue where as far I know the following will not open on my computer:
- Start Menu
- Action/Notification Centre
- Any UWP/Store app (including settings, the microsoft store and defender)
When attempting to open settings and the microsoft store via the run box I encountered this error message file system error (-2144927436).
So far I have attempted running sfc /scannow and dism /Online /Cleanup-Image /RestoreHealth (and restarting on the completion of DISM).
I am aware of other threads with a similar issue but a different code, however the fix has always been that mentioned above (DISM and sfc) which hasn’t worked.
Thankyou in advance!
I’m John an Independent Advisor and a Microsoft user like you. I’ll be happy to assist you today. I understand you have a problem with File System Error after update. When was the last time it worked properly? Have you made any changes recently?
Please try the suggested methods below on your main account.
**Run the troubleshooter:
Select the Start button, and then select Settings > Update & Security > Troubleshoot, click Additional troubleshooters and then from the list select Windows Store apps > Run the troubleshooter.
**Reset the Microsoft Store cache
Press the Windows Logo Key + R to open the Run dialog box, type wsreset.exe, and then select OK.
Note
A blank Command Prompt window will open, and after about ten seconds the window will close and Microsoft Store will open automatically.
**Re-register built-in apps via Powershell
Windows key+X then select Windows Powershell (Admin)
copy paste the command below one at a time then press Enter. Please ignore the red errors and let the process complete.
Get-AppxPackage Microsoft.Windows.ShellExperienceHost | foreach
Restart your Computer
Kindly let me know if this helps or if you have any further concerns.
Ошибка 2147942402 windows 10
Общие обсуждения
На одном ПК перестали устанавливаться ежемесячные обновления качества, начиная с августа 2017. ОС Windows 7 SP1.
Ошибки wusa (пытаюсь установить обнову kb4054518):
Не удается установить обновление Windows «Обновление системы безопасности для ОС Windows (KB4054518)» из-за ошибки: 2147942402 «Не удается найти указанный файл.» (Командная строка: «»C:Windowssystem32wusa.exe» «C:kb4054518.msu» «)
C:>dism.exe /online /add-package /packagepath:c:temp4054518windows6.1-kb4054518-x64.cab
Cистема DISM
Версия: 6.1.7600.16385
Версия образа: 6.1.7600.16385
Обрабатывается 1 из 1 — Добавление пакета Package_for_RollupFix
7601.23964.1.2
[===========================65.9%====== ]
Произошла ошибка — «Package_for_RollupFix» Ошибка: 0x80070002
Не удается найти указанный файл.
Файл журнала DISM находится по адресу C:WindowsLogsDISMdism.log
2017-12-20 11:49:14, Info DISM DISM Package Manager: PID=4044 Encountered the option «packagepath» with value «c:temp4054518windows6.1-kb4054518-x64.cab» — CPackageManagerCLIHandler::Private_GetPackagesFromCommandLine
2017-12-20 11:49:17, Info DISM DISM Package Manager: PID=4044 Package Package_for_RollupFix
7601.23964.1.2 with CBS state 2(CbsInstallStateResolved) being mapped to dism state 1(DISM_INSTALL_STATE_NOTPRESENT) — CDISMPackage::LogInstallStateMapping
2017-12-20 11:49:17, Info DISM DISM Package Manager: PID=4044 Initiating Changes on Package with values: 4, 7 — CDISMPackage::Internal_ChangePackageState
2017-12-20 11:50:45, Info DISM DISM Package Manager: PID=4044 Error in operation: (null) (CBS HRESULT=0x80070002) — CCbsConUIHandler::Error
2017-12-20 11:50:45, Error DISM DISM Package Manager: PID=4044 Failed finalizing changes. — CDISMPackageManager::Internal_Finalize(hr:0x80070002)
2017-12-20 11:50:45, Error DISM DISM Package Manager: PID=4044 Failed processing package changes — CDISMPackageManager::ProcessChanges(hr:0x80070002)
2017-12-20 11:50:45, Info DISM DISM Package Manager: PID=4044 Loaded servicing stack for online use only. — CDISMPackageManager::RefreshInstanceAndLock
2017-12-20 11:50:45, Error DISM DISM Package Manager: PID=4044 Failed while processing command add-package. — CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80070002)
2017-12-20 11:50:45, Info DISM DISM Package Manager: PID=4044 Further logs for online package and feature related operations can be found at %WINDIR%logsCBScbs.log — CPackageManagerCLIHandler::ExecuteCmdLine
2017-12-20 11:50:45, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80070002
2017-12-20 11:50:45, Info DISM DISM Image Session: PID=4044 Disconnecting the provider store — CDISMImageSession::Final_OnDisconnect
2017-12-20 11:50:45, Info DISM DISM Provider Store: PID=4044 Finalizing the servicing provider(DISM Package Manager) — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:45, Info DISM DISM Package Manager: PID=4044 Finalizing CBS core. — CDISMPackageManager::Finalize
2017-12-20 11:50:45, Info DISM DISM Provider Store: PID=4044 Disconnecting Provider: DISM Package Manager — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Found the OSServices. Waiting to finalize it until all other providers are unloaded. — CDISMProviderStore::Final_OnDisconnect
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Finalizing the servicing provider(MsiManager) — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Disconnecting Provider: MsiManager — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Finalizing the servicing provider(IntlManager) — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Disconnecting Provider: IntlManager — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Found the PE Provider. Waiting to finalize it until all other providers are unloaded. — CDISMProviderStore::Final_OnDisconnect
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Finalizing the servicing provider(DriverManager) — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Disconnecting Provider: DriverManager — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Finalizing the servicing provider(DISM Unattend Manager) — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Disconnecting Provider: DISM Unattend Manager — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Found the OSServices. Waiting to finalize it until all other providers are unloaded. — CDISMProviderStore::Final_OnDisconnect
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Finalizing the servicing provider(SmiManager) — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Disconnecting Provider: SmiManager — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Finalizing the servicing provider(Edition Manager) — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Disconnecting Provider: Edition Manager — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Releasing the local reference to OSServices. — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Disconnecting Provider: OSServices — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Releasing the local reference to DISMLogger. Stop logging. — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:51:00, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2017-12-20 11:51:00, Info DISM DISM.EXE:
2017-12-20 11:51:00, Info DISM DISM.EXE:
SFC /scannow проблем не находит.
Помогите, пожалуйста, разобраться в чем проблема? Заранее спасибо!
Ошибка 2147942402 windows 10
Общие обсуждения
На одном ПК перестали устанавливаться ежемесячные обновления качества, начиная с августа 2017. ОС Windows 7 SP1.
Ошибки wusa (пытаюсь установить обнову kb4054518):
Не удается установить обновление Windows «Обновление системы безопасности для ОС Windows (KB4054518)» из-за ошибки: 2147942402 «Не удается найти указанный файл.» (Командная строка: «»C:Windowssystem32wusa.exe» «C:kb4054518.msu» «)
C:>dism.exe /online /add-package /packagepath:c:temp4054518windows6.1-kb4054518-x64.cab
Cистема DISM
Версия: 6.1.7600.16385
Версия образа: 6.1.7600.16385
Обрабатывается 1 из 1 — Добавление пакета Package_for_RollupFix
7601.23964.1.2
[===========================65.9%====== ]
Произошла ошибка — «Package_for_RollupFix» Ошибка: 0x80070002
Не удается найти указанный файл.
Файл журнала DISM находится по адресу C:WindowsLogsDISMdism.log
2017-12-20 11:49:14, Info DISM DISM Package Manager: PID=4044 Encountered the option «packagepath» with value «c:temp4054518windows6.1-kb4054518-x64.cab» — CPackageManagerCLIHandler::Private_GetPackagesFromCommandLine
2017-12-20 11:49:17, Info DISM DISM Package Manager: PID=4044 Package Package_for_RollupFix
7601.23964.1.2 with CBS state 2(CbsInstallStateResolved) being mapped to dism state 1(DISM_INSTALL_STATE_NOTPRESENT) — CDISMPackage::LogInstallStateMapping
2017-12-20 11:49:17, Info DISM DISM Package Manager: PID=4044 Initiating Changes on Package with values: 4, 7 — CDISMPackage::Internal_ChangePackageState
2017-12-20 11:50:45, Info DISM DISM Package Manager: PID=4044 Error in operation: (null) (CBS HRESULT=0x80070002) — CCbsConUIHandler::Error
2017-12-20 11:50:45, Error DISM DISM Package Manager: PID=4044 Failed finalizing changes. — CDISMPackageManager::Internal_Finalize(hr:0x80070002)
2017-12-20 11:50:45, Error DISM DISM Package Manager: PID=4044 Failed processing package changes — CDISMPackageManager::ProcessChanges(hr:0x80070002)
2017-12-20 11:50:45, Info DISM DISM Package Manager: PID=4044 Loaded servicing stack for online use only. — CDISMPackageManager::RefreshInstanceAndLock
2017-12-20 11:50:45, Error DISM DISM Package Manager: PID=4044 Failed while processing command add-package. — CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80070002)
2017-12-20 11:50:45, Info DISM DISM Package Manager: PID=4044 Further logs for online package and feature related operations can be found at %WINDIR%logsCBScbs.log — CPackageManagerCLIHandler::ExecuteCmdLine
2017-12-20 11:50:45, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80070002
2017-12-20 11:50:45, Info DISM DISM Image Session: PID=4044 Disconnecting the provider store — CDISMImageSession::Final_OnDisconnect
2017-12-20 11:50:45, Info DISM DISM Provider Store: PID=4044 Finalizing the servicing provider(DISM Package Manager) — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:45, Info DISM DISM Package Manager: PID=4044 Finalizing CBS core. — CDISMPackageManager::Finalize
2017-12-20 11:50:45, Info DISM DISM Provider Store: PID=4044 Disconnecting Provider: DISM Package Manager — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Found the OSServices. Waiting to finalize it until all other providers are unloaded. — CDISMProviderStore::Final_OnDisconnect
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Finalizing the servicing provider(MsiManager) — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Disconnecting Provider: MsiManager — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Finalizing the servicing provider(IntlManager) — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Disconnecting Provider: IntlManager — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Found the PE Provider. Waiting to finalize it until all other providers are unloaded. — CDISMProviderStore::Final_OnDisconnect
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Finalizing the servicing provider(DriverManager) — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Disconnecting Provider: DriverManager — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Finalizing the servicing provider(DISM Unattend Manager) — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Disconnecting Provider: DISM Unattend Manager — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Found the OSServices. Waiting to finalize it until all other providers are unloaded. — CDISMProviderStore::Final_OnDisconnect
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Finalizing the servicing provider(SmiManager) — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Disconnecting Provider: SmiManager — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Finalizing the servicing provider(Edition Manager) — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Disconnecting Provider: Edition Manager — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Releasing the local reference to OSServices. — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Disconnecting Provider: OSServices — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:50:59, Info DISM DISM Provider Store: PID=4044 Releasing the local reference to DISMLogger. Stop logging. — CDISMProviderStore::Internal_DisconnectProvider
2017-12-20 11:51:00, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2017-12-20 11:51:00, Info DISM DISM.EXE:
2017-12-20 11:51:00, Info DISM DISM.EXE:
SFC /scannow проблем не находит.
Помогите, пожалуйста, разобраться в чем проблема? Заранее спасибо!
Содержание
- question
- Windows 10 20H2 Install Update Fails with Error 2147942402
- 4 Answers
- Ошибка 2147942402 windows 10
- Вопрос
- Все ответы
- Windows Update issue: Error 2147942402
- 4 Replies
- Ошибка 2147942402 windows 10
- Не устанавливаются KB4519976 и KB4520003 — решение проблемы
- Статьи по теме:
- Комментарии: 8 к “Не устанавливаются KB4519976 и KB4520003 — решение проблемы”
question
Windows 10 20H2 Install Update Fails with Error 2147942402
This install has been failing for some time now, and I find that I’m currently at 1909, which is now out of service.
Looking at the Event Viewer, I see this:
ErrorCode 2147942402
ErrorString The system cannot find the file specified.
CommandLine «C:WINDOWSsystem32wusa.exe» Windows8-RT-KB2937636-x86 /quiet
I downloaded KB2937636, but the install failed as it’s for Windows 8.
The question I have is: Why is Win 10 20H2 trying to install a Win 8 KB update?
4 Answers
Most end users do not understand the update error messages or codes.
And many helpers must continue to learn about new messages and codes.
Some update or upgrade messages are easy and others are complex.
If you choose to clean install then backup files to another disk drive or the cloud.
This is information on clean install:
Reset save files, Custom install (saves files similar to a reset save files) and Windows refresh tutorials can also be provided.
Again some troubleshooting can be easy and others can be complex.
Files are collected then trial and error steps are performed.
.
.
.
.
.
Please remember to vote and to mark the replies as answers if they help.
On the bottom of each post there is:
Propose as answer = answered the question
On the left side of each post: Vote = a helpful post
.
.
.
.
.
It is very strange. Indeed the KB2937636 it is a cumulative update for 2012/8 that has nothing to do with 20H2. Could it be a pending update that is superseded, but since it failed back in the day it still appears pending before the 20H2?
I would try to rebuild the update repository this way:
If after this still gives you error I would try with a health image restore using DISM: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/repair-a-windows-image
—If the reply is helpful, please Upvote and Accept as answer—
Thank you for the reply, LimitlessTechnology-2700.
I issued the commands in Powershell, and they all completed successfully.
I then launched the Windows Upgrader program, which then started installing 21H1 instead of 20H2 as before.
As before, it hits 99% and then hangs.
The only action I can take is to end the program with Task Manager.
Event Viewer shows:
The program Windows10UpgraderApp.exe version 1.4.9200.23367 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: 1730
Start Time: 01d7bac7c399b30c
Termination Time: 4294967295
Application Path: C:Windows10UpgradeWindows10UpgraderApp.exe
Report Id: 571653e4-0ce4-48b0-8660-854ce0e9b2ac
Faulting package full name:
Faulting package-relative application ID:
Hang type: Top level window is idle
I might have to do a Win 10 install from scratch.
Please indicate whether you want to troubleshoot or clean install.
Troubleshooting will require running log collectors and trial and error steps.
Clean install will require the creation of a windows 10 iso flash drive, saving important files to another disk drive or the cloud, installation of the new operating system, installation of new drivers, installation of applications.
.
.
.
.
.
Please remember to vote and to mark the replies as answers if they help.
On the bottom of each post there is:
Propose as answer = answered the question
On the left side of each post: Vote = a helpful post
.
.
.
.
.
Источник
Ошибка 2147942402 windows 10
Вопрос
Event Details: Task Scheduler failed to start «MicrosoftWindowsCertificateServicesClientUserTask» task for user «Domainuserxx». Additional Data: Error Value: 2147942402.
Все ответы
If those errors are appearing in the Server Event Logs, please post up the Event Id and the Source, and identify which is which. Or, you can go to www.eventid.net and research them yourself. If you have, and there is no info, then tell us that.
-Please post the resolution to your issue so others may benefit.
-Get Your SBS Health Check at www.sbsbpa.com
Event Details: Task Scheduler failed to start
«MicrosoftWindowsCertificateServicesClientUserTask» task for user
«Domainuserxx». Additional Data: Error Value: 2147942402.
-Kevin Weilbacher (SBS MVP) «The days pass by so quickly now, the nights are seldom long»
http://msmvps.com/blogs/kwsupport/default.aspx
I was desperately trying to solve this issue and tried procedure from the link below, but with no luck. Would somebody try it to make sure it is 100% not working for this particular issue?
the link: http://davidcmoisan.wordpress.com/2010/11/14/resolving-%E2%80%9Cpautoenr-dll-raised-an-exception%E2%80%9D/
Well that one looks pretty frightening to do? These are the only two errors I got today.
What is the consequence of ignoring them? Or maybe I should just restart the server on a regular basis?
Many thanks for your time.
Robert Pearman SBS MVP (2011) | www.titlerequired.com | www.itauthority.co.uk
Well I also had the error when trying to reschedule a Job (trigger One time) Windows 2008 R2
Initial Error Message comming from the task scheduler was :
The following error was reported: The referenced account is currently locked out and may not be logged on to..
In the event view for TaskScheduler I had 2 errors:
Task Scheduler failed to start “MicrosoftWindowsCertificateServicesClientUserTask” task for user “username”. Additional Data: Error Value: 2147942402.
The user in question was disconnected for many days, no schedule task created or running under this user and account was not locked, I logged off the user, still had the issue.
What I did to solve it:
First when to my task, I changed the User or Groups under the General tab
Selected Run only When user is logged on then click on OK
After that I was able to reschedule my job.
Put back Run whether user is logged on or not.
everything is now back to normal.
Источник
Windows Update issue: Error 2147942402
Windows update «Security Update for Windows (KB4015549)» could not be installed because of error 2147942402 «The system cannot find the file specified.» (Command line: «»C:Windowssystem32wusa.exe» «C:AMD64-all-windows6.1-kb4015549-x64.msu» «)
I’ve tried removing cache.. restarting services.. turning off unnecessary services..
any help appreciated
The help desk software for IT. Free.
Track users’ IT needs, easily, and with only the features you need.
Ugh. 4015549 broke software by Open Text and gave me some heartache from it.
I’m assuming the update is actually stored in that location at the root of C:?
If so, I’ve used these instructions for single odd cases just to get them shoved into the system so I can move about my day: https://blogs.technet.microsoft.com/askcore/2011/02/15/how-to-use-dism-to-install-a-hotfix-from-with.
yes it was on C:.. i tried a couple different logins and locations.. i’ll try the DISM tool in your link..thanks
Ugh. 4015549 broke software by Open Text and gave me some heartache from it.
I’m assuming the update is actually stored in that location at the root of C:?
If so, I’ve used these instructions for single odd cases just to get them shoved into the system so I can move about my day: https://blogs.technet.microsoft.com/askcore/2011/02/15/how-to-use-dism-to-install-a-hotfix-from-with.
I’m not the elegant problem solver that generally mills around here. My solutions tend to be like the big nasty hammer you keep around in case you need to perform some percussive maintenance on a contraption from the 1950s.
I’ve generally had good luck unpacking the update and manually installing the cab files, it bypasses whatever is causing wusa to flip out.
Ugh. 4015549 broke software by Open Text and gave me some heartache from it.
I’m assuming the update is actually stored in that location at the root of C:?
If so, I’ve used these instructions for single odd cases just to get them shoved into the system so I can move about my day: https://blogs.technet.microsoft.com/askcore/2011/02/15/how-to-use-dism-to-install-a-hotfix-from-with.
PS C:kb1> Dism.exe /online /add-package /packagepath:c:kb1Windows6.1-KB4015549-x64.cab
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
Image Version: 6.1.7601.18489
Источник
Ошибка 2147942402 windows 10
Сообщения: 1
Благодарности:
Один из вариантов
Невозможно подключиться к принтеру Kyocera FS-1020MFP »
——-
Скоро станет на одного Линуксоида больше!
» width=»100%» style=»BORDER-RIGHT: #719bd9 1px solid; BORDER-LEFT: #719bd9 1px solid; BORDER-BOTTOM: #719bd9 1px solid» cellpadding=»6″ cellspacing=»0″ border=»0″>
Сообщения: 1
Благодарности:
Приветствую, присоединяюсь к проблеме.
комп, на котором рашарен принтер, видится, принтер видится, но не подключается
-дрова переустанавливал
-службы в порядке
-принтер видится по сети
-в АД видится
-по локальному порту не подключается
ошибка как у ТС, на обоих машинах win 10 pro
Сообщения: 2
Благодарности: 2
» width=»100%» style=»BORDER-RIGHT: #719bd9 1px solid; BORDER-LEFT: #719bd9 1px solid; BORDER-BOTTOM: #719bd9 1px solid» cellpadding=»6″ cellspacing=»0″ border=»0″> » width=»100%» style=»BORDER-RIGHT: #719bd9 1px solid; BORDER-LEFT: #719bd9 1px solid; BORDER-BOTTOM: #719bd9 1px solid» cellpadding=»6″ cellspacing=»0″ border=»0″>
Сообщения: 25794
Благодарности: 4315
Сообщение оказалось полезным? Поблагодарите автора, нажав ссылку 
Полезное сообщение чуть ниже.
Источник
Не устанавливаются KB4519976 и KB4520003 — решение проблемы
По недоброй традиции последних месяцев пользователи Windows 7 и Windows Server 2008 R2 столкнулись с ошибками при установке обновлений KB4519976 и KB4520003 (ежемесячные пакеты обновлений). Впрочем, исправить данные ошибки совсем не сложно.
Как известно, с недавних пор корпорация Microsoft подписывает новые обновления для Windows 7 и Windows Server 2008 R2 только при помощи алгоритма SHA-2. Отсюда следует, что, если своевременно не подготовить операционную систему к таким переменам, новые патчи на неё устанавливаться не будут. Хорошая новость заключается в том, что эти подготовительные мероприятия просты. Достаточно установить несколько обновлений.
Рекомендации с сайта Microsoft.
Перед установкой KB4519976 и/или KB4520003 Microsoft рекомендует установить KB4490628 и KB4474419. Также проверьте, что у вас установлены KB4516655 и (по собственному опыту) KB3133977.
При соблюдении этих условий установка KB4519976 и/или KB4520003 должна пройти в штатном режиме.
Этот «вторник обновлений» оказался не слишком богатым на устранённые уязвимости. Из потенциально опасных следует выделить уязвимости CVE-2019-1238 и CVE-2019-1239, связанные с тем, как VBScript обрабатывает объекты в памяти. Эксплуатируя данные уязвимости, злоумышленник может выполнить произвольный код в контексте текущего пользователя.
Очередная уязвимость (CVE-2019-1333) была найдена и в RDP. Проблема проявляется на стороне клиента и позволяет атакующему добиться удалённого выполнения кода. Однако для этого нужно убедить жертву подключиться к вредоносному серверу.
Несмотря на то, что в этом месяце не зафиксировано уязвимостей нулевого дня, девять багов получили статус критических. Поэтому с установкой обновлений всё таки лучше не тянуть.
Статьи по теме:
Комментарии: 8 к “Не устанавливаются KB4519976 и KB4520003 — решение проблемы”
KB4519976 не устанавливается, хотя все условия перед установкой выполнено. При чем это не на одном ПК. Так что не хватает еще чего-то.
Какой код ошибки? Запускается ли средство восстановления системы?
Код ошибки 800700B7. Начиная с августа, когда Майкрософт ввела подпись SHA-2, перестали устанавливаться ежемесячные пакеты обновлений. Пришлось их начинать скрывать.
Для корректной работы с SHA-2 нужны патчи, которые перечислены в статье. Я правильно понял, что на всех этих компьютерах они корректно установились? Других патчей Microsoft не предлагает. Способ лично успешно опробован в локальной сети с WSUS и десятками ПК.
Если вы распространяете обновления на ПК с WSUS, попробуйте для интереса скачать ежемесячный пакет и установить его на одной из машин вручную. Естественно, предварительно должны быть установлены все KB из этой статьи.
В целом, код 0x800700b7 является обобщённым. Как правило, он говорит о повреждённых системных файлах или о некорректных записях в реестре. Если вручную ежемесячный пакет установится успешно, очистите папку %WINDIR%SoftwareDistributionDownload, чтобы обновления с WSUS на компьютеры загрузились вновь.
Также можно использовать команду sfc /scannow, чтобы провести проверку и восстановление отсутствующих или повреждённых системных файлов.
Да требуемые патчи установились. Вручную пакеты KB4512506, KB4516065, KB 4524157, KB4519976 не устанавливаются при условии установленных патчей. Результат команды sfc /scannow: Защита ресурсов Windows не обнаружила нарушений целостности. Очистку папки SoftwareDistribution делал. Началось все с запуска средства восстановления системы после не установившихся KB4512506 и KB4512486.
Что самое интересное KB4520003 установилось, прилетев от WSUS. И ряд других обновлений тоже установилось. Не устанавливаются только Monthly Rollup.
Выполнил все указанные инструкции дважды с интервалом в месяц.
Чистил папку %WINDIR%SoftwareDistributionDownload, запускал sfc /scannow, устанавливал через центр обновления и скачивал из каталогов. Все тщетно. Указанные обновления уже установлены, а Monthly Rollup по-прежнему устанавливается до 100%, а затем откатывается с сообщением «Не удалось установить обновление.»
Думаю статьи в этом не виноват — просто Microsoft пытается принудить нас к установке W10.
Источник
Adblock
detector