Не удалось запустить dcom сервер ошибка 2147942402

Getting error 2147942402 (0x80070002) while launching recently downloaded WSL (Ubuntu 22.04). I recently downloaded the lasted Ubuntu WSL from the Microsoft store and, when I am trying to open the terminal, it shows an error code.

However, I have found the solution to fix the error of this problem. Perhaps this error is caused because you have already installed an Ubuntu WSL of a different version or incorrectly configured the command line for a particular WSL.

So, to fix this error you must follow the steps, which I have explained in this article:

Step: 1. Open Windows Terminal Setting

First of all, you will need to be installed a WSL distribution (In this tutorial we have used Ubuntu 22.04 LTS). As you have seen the error image while opening the in the Windows Terminal. So, open the Windows Terminal settings as shown in the image above. Now follow the next step.

Step: 2. Select WSL, which shows the error

Select the WSL which is showing an error from the sidebar as shown in the image above. When you click on the WSL, you will see the command line location for the distributions. The location will be incorrectly configured, and you must set the complete WSL location to work properly.

Step: 3. Change Proper WSL Location to Access in Terminal

Now, click on the command line section to correct the WSL’s proper location, as you can see in the image above. You must add the full executable location. In case you are getting errors for a different version of Ubuntu distro or Debian, you can just take the example location as mentioned below.

C:Windowssystem32wsl.exe -d Ubuntu-22.04

In case you have Ubuntu 20.04, Ubuntu 18.04 or Debian then you have to replace it with a proper distribution name.

Must Read: How to Fix Missing Sign-in Options on Windows 10?

Wrapping up

After all, when you define the correct location and save, and open the terminal with your WSL distro, no error shows again. Now you can use the terminal for your Linux system normally and without any errors.

So, this tutorial ends here, but if you get any error regarding WSL or Linux terminal you can ask in the comment box.

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

I can’t believe this issue is here since 2009, but the error Background Intelligent Transfer Service service terminated with service-specific error 2147942402 is still a very common phenomenon. I used to have this error in conjunction with Automatic Updates on a Windows 2003 server and Windows XP client. And yet you may face it on Windows 10, 2016 or even 2019.

So here’s the original story.

I was running WSUS in my domain, but the updates didn’t arrive. A quick investigation resulted in A LOT OF ERRORS in the event viewer. For a couple of days, the following error had returned every one or two minutes or so!

The Background Intelligent Transfer Service service terminated with service-specific error 2147942402 (0x80070002).

Event Type:       Error
Event Source:    Service Control Manager
Event Category: None
Event ID:          7024
Date:                3/31/2009
Time:                3:48:14 PM
User:                N/A
Computer:         computer name
Description:
The Background Intelligent Transfer Service service terminated with service-specific error 2147942402 (0x80070002).

In my case, I couldn’t get the Background Intelligent Transfer Service started again. The following error messages showed up every time:

Windows could not start the Background Intelligent Transfer Service on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code -2147024893.

If you see the same error in your event log (event 7024), you should know that there are a lot of possible solutions. Now, I do not feel embarrassed to tell you that I checked almost every solution available on the internet and spent quite some time on this issue. So, because of all the effort I have put into this problem, I decided to sum up all the solutions for you I’ve tried. Hopefully, it will help you solving this BITS error.

After each step, try to start the BITS service. If it doesn’t start successfully, just continue with the next step

Step 1:
Open services.msc and check that the following services are set to start Manual or Automatic:

Terminal Services
Remote Procedure Call (RPC)
System Event Notification
Windows Management Instrumentation Driver Extensions
COM+ Event System
DCOM Server Process Launcher

Also make sure that service Workstation is Running. And next try to start the BITS service.

Fixed it? Leave a comment
Problem not fixed yet? Continue to step 2!

Step 2:
Delete the Downloader folder. You can find the downloader folder in the following location:
“C:Documents and SettingsAll UsersApplication DataMicrosoftNetworkDownloader”
The Application Data folder is hidden by default, so if you don’t see the Application Data folder, go to folder options and check the option Show Hidden Files and Folders

Next try to start the BITS service.

Fixed it? Leave a comment
Problem not fixed yet? Continue to step 3!

Step 3:
Delete all content of the SoftwareDistribution folder (do NOT delete the folder itself, only the content!). You can find the downloader folder in the following location:
“C:WindowsSoftwareDistribution”

Next try to start the BITS service.

Fixed it? Leave a comment
Problem not fixed yet? Continue to step 4!

Step 4:
Register 8 dll files that are directly connected to BITS. Some applications remove or corrupt the dll files which cause the BITS service to fail. To register the dll files easily, do the following:

1. Open Notepad
2. Copy and paste the following entries into the text document.
   regsvr32 oleaut32.dll
   regsvr32 jscript.dll
   regsvr32 vbscript.dll
   regsvr32 msxml.dll
   regsvr32 softpub.dll
   regsvr32 wintrust.dll
   regsvr32 initpki.dll
   regsvr32 cryptdlg.dll
3. Save this file as a batch file
   – click on save as
   – open the drop down box at the bottom to read save as file type: all files
   – name of file: BITS_fix.bat (the .bat is creating a batch file)
   – run the BITS_fix.bat  (double-click)

Next try to start the BITS service.

Fixed it? Leave a comment
Problem not fixed yet? Continue to step 5!

Step 5:

Deregister and reregister the qmgr.dll and qmgrprxy.dll. To register these files, open a command prompt and type the following:
regsvr32 qmgr.dll [ENTER]
regsvr32 qmgrprxy.dll [ENTER]

I hope you had success. If not, feel free to post a comment. You’re not the only one who’s struggling with BITS
Oh, by the way, if you DID have success, feel free to post a comment too. I love “thank you”-messages

Sometimes when you run some scripts to tweak the default functionalities of Windows, you might face the DCOM errors with error code 10001.

This error code has several variations like:

Unable to start a DCOM server 2147942402

Unable to start a DCOM server event ID 10001

What is DCOM?

DCOM (Distributed Component Object Model) is a service that allows computers to run programs on the network as if they’re running locally. As you can see, this is a sensitive service because it is closely related to the proper working of the Windows operating system. Hence, we don’t recommend tweaking the permissions and settings of DCOM in any condition.

Still, if you want to tweak the permissions of DCOM to resolve a particular or 10001 error code, then you should understand the reason for that error code first.

When Does the DCOM Error 10001 Occur?

This error code mostly occurs:

• When you execute some scripts to disable Cortana or the software keyboard in Windows 10. That is why people also call it the 10001 windows 10 error.
• After installing a fresh copy of Windows in some cases.
• When updating Windows applications like the Windows store.

Pre-requisite

Before we move on to tweaking your registries, you should first check whether your local Antivirus isn’t conflicting or quarantining the application files through which you are encountering the error message.

According to a user, his Microsoft Store files were quarantined by Zemana Antilogger and he wasn’t notified. This occurred after he initiated the process to update the Store application. No matter which Antivirus you are using, make sure to check the directories or files it is black-listing.

You can check our guide on How to Disable your Antivirus.

How to Solve DCOM Error 10001?

In this series of steps, we will demonstrate how to resolve the error message w.r.t the InputService. This is one of the use-cases and you can freely replace it with the other application you are having the error with.

1. First, disable the startup of ‘InputService‘ (or any other app if you’re solving some other error code with DCOM).
2. Now, open the ‘Component Services’ console from the Start menu.
   

Copying the ‘App ID’ from ‘Component Services’

1. In the new window, expand the ‘Component Services,’ then ‘Computers.’
2. Now, expand the ‘My Computer’ and then, ‘DCOM Config.’
   
3. Right-click on the service you need to change inside DCOM Config and choose the ‘Properties’ option.
4. Now, jot down the ‘Application Name’ and ‘Application ID’ in the properties window of that particular service.
   

Note: Copy the ‘Application ID’ here because we will need it later on

Changing the Permissions of that Particular ‘App ID’ in ‘Registry Editor’

Note: Modifying the permissions of a particular service can break some functionalities in Windows so make sure you follow the steps correctly.

1. After that, minimize the opened windows and go to the ‘Registry Editor.’
   
2. Click on the ‘HKEY_CLASSES_ROOT’ folder inside the ‘Computer’ section and paste the copied (jotted down) ‘App ID’ after ‘ComputerHKEY_CLASSES_ROOT.’
3. Hitting the ‘Enter’ key will take you to that particular key in the registry editor.
   
4. Now, right-click on the folder that has the same ‘App ID’ and choose the ‘Permissions’ option.
   
5. Then, click on the ‘Advanced’ button in the ‘Permissions…’ window.
   
6. Now, you will notice that the Owner/account type is ‘TrustedInstaller.’ So, click on the ‘Change’ option to change the ownership.
   
7. Then, change the ownership to the ‘Local Administrator group’ or some applicable owner and click on ‘Apply’ to save the new changes.
8. After that, click on the ‘OK’ button to close this window.
9. Now, choose the ‘Local Administrators group’ under the ‘Security’ tab of the ‘Permissions…’ window.
10. Then, check the ‘Allow’ box for ‘Full Control’ in the ‘Permissions for Administrators’ section in the same window.
11. After that, click ‘Apply’ to save the changes.
    
12. Now, close the ‘Component Services’ console and everything else.
13. After that, reopen the ‘Component Services’ console and try to change the ‘Launch and Activation Permissions’ from the ‘Security’ tab of the applications’ properties.

Note: You need to deny all the permissions for ‘InputService’ to resolve the DCOM error 10001

Conclusion

This procedure is dangerous for your operating system because it can break your Windows and you may need to reinstall the Windows. So, we don’t recommend trying this solution at all because it is better to play safe. Still, if you want to tweak the permissions of ‘DCOM Config,‘ this procedure is the only one that has worked for others.