I've upgraded my Windows 7 to Windows 10. Initially everything worked. Then I removed windows.old folder, removed some windows components and may be did something else. As a result BITS service cannot start with error 1053. 2 messages are appended to event log: 7009 and 7000. Strange that system writes that 30000 ms period is exceeded though the error appears immediately (not more than in 1000 ms)

Does anybody have ideas how to fix it?

Hi,

Firstly, please make sure its dependencies services(DCOM Server Process Launcher and RPC Endpoint Mapper) running fine.

If both are running fine, we could try to reset the Windows Update Components to check the result.

How do I reset Windows Update components?

https://support.microsoft.com/en-in/kb/971058

Firstly, please make sure its dependencies services(DCOM Server Process Launcher and RPC Endpoint Mapper) running fine.

If both are running fine, we could try to reset the Windows Update Components to check the result.

Yes, both DCOM Server Process Launcher and RPC Endpoint Mapper are running and RPC is running too

When I reset WU components the following errors occurs:

1. At the step 4 catroot2 folder cannot be renamed because it's is locked by some process (I dont know which). I think that kb article is for windows versions prior 10 and for win10 another additional services should be stopped to unlock catroot2 folder

2. At step 6 regsvr32 outs errors for some dlls:

<style type="text/css">P { margin-bottom: 0.21cm; }</style>

DLLRegisterServer entry point not found:

mshtml.dll

shdocvw.dll

browseui.dll

wuaueg.dll

qmgr.dll

Dll not found:

msxml.dll

gpkcsp.dll

sccbase.dll

slbcsp.dll

initpki.dll

wuaueng1.dll

wucltui.dll

wuweb.dll

qmgrprxy.dll

wuctlux.dll

muweb.dll

wuwebv.dll

And final result is that problem is not resolved

I tried to reset WU components once again and only the following problems remain:

When I reset WU components the following errors occurs:

At step 6 regsvr32 outs errors for some dlls:

DLLRegisterServer entry point not found:

mshtml.dll

shdocvw.dll

browseui.dll

wuaueg.dll

qmgr.dll

Dll not found:

msxml.dll

gpkcsp.dll

sccbase.dll

slbcsp.dll

initpki.dll

wuaueng1.dll

wucltui.dll

wuweb.dll

qmgrprxy.dll

wuctlux.dll

muweb.dll

wuwebv.dll

And final result is that problem is not resolved

And final result is that problem is not resolved

Those regsvr32 commands are more obsolete now than they were when they were first given years ago although it appears they have fixed some of the original script's most egregious errors.  These defects had been hidden in the Windows Update troubleshooter but it was broken when Windows became 10, thus being less than Windows 7.  I don't know if that problem has been resolved yet.

What I'm curious about is what is the state of  bitsadmin /util  now?  That used to provide us a way of repairing BITS but that is obviously gone, supposedly replaced by PowerShell commands. 

Administrative tools for the BITS service are now provided by BITS PowerShell cmdlets.

So, what are they?  For the Util Repair functions, not the standard BITS functions.

Have your tried How do I reset Windows Update components?

Have your tried How do I reset Windows Update components?

You have just answered my first question.  Instead of worrying about fixing the script embedded in the troubleshooter they are now providing a manual procedure.  Problem solved.

Thanks to your link I have just re-downloaded the package and found the same problem that I remembered seeing:

Found in %TEMP%\msdtadmin\...\cl_windowsversion.ps1
(while the Run prompt is up)

function checkWindowsVersion8(){
	# check the version of windows
	
	$OS = Get-WmiObject -Namespace root\CIMV2 -Class Win32_OperatingSystem
	if($OS)
	{
		if( ([int]::Parse($OS.version[0]) -ge 6) ){
			return ( [int]::Parse($OS.version[0])*10 + [int]::Parse($OS.version[2])  ) # greater than windows vista

And in W10 PowerShell

PS>(Get-WmiObject -Namespace root\CIMV2 -Class Win32_OperatingSystem).Version
10.0.10240

Oops. If only they hadn't called it Windows 10.   <eg>

What I'm curious about is what is the state of  bitsadmin /util  now?  That used to provide us a way of repairing BITS but that is obviously gone, supposedly replaced by PowerShell commands. 

Administrative tools for the BITS service are now provided by BITS PowerShell cmdlets.

So, what are they?  For the Util Repair functions, not the standard BITS functions.

At a guess, bitsadmin /util /repairservice https://msdn.microsoft.com/en-us/library/aa362813(v=vs.85).aspx would have been replaced by pkgmgr and DISM, around the Vista timeframe, since BITS became an OS component around then.

So to repair BITS, would probably be an SFC or DISM method, these days, maybe these might help that:

http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_install/how-to-repair-your-system-files-using-dism-and-sfc/1021b42a-09ff-41a0-a95a-48f3ee3ae699?auth=1

http://www.tenforums.com/tutorials/7808-dism-repair-windows-10-image.html