BITS service keeps stopping

Trying to install 11803 update.
OLE error 80248007
MS error codes page says "Info requested is not in data store,"
whatever that means.

Ran windows update troubleshooter.
It said "Starting bits service" ... forever.

Summary of Windows Update Troubleshooter showed no issues except
"Suggested- network reset." Don' t think that will help. I was able to
search the error code OK.

Went to services in task Manager. Right-clicked BITS, which was
stopped, selected Start. It showed "Running" for a second, then
reverted to Stopped. While I was looking at it, this same thing
happened (Update Troubleshooter started it?) I tried starting it
manually again. Again, Running then reversion to Stopped.

I found, downloaded and ran the Microsoft BITS repair tool from
https://support.microsoft.com/en-us/...ransfer-servic
This says for VISTA but also says it was Updated 04/18, so I presume
it is also for WIn10. Note: Several pages say to find this
troubleshooter from START-troubleshoot-View All. Mine has no "view
all." There is "Find and fix other problems," but nothing there for
BITS.

Running the downloaded tool resulted in "BITS repair not required
currently."


So what could be stopping it BITS?


-dan z-




--
Someone who thinks logically provides
a nice contrast to the real world.
(Anonymous)

slate_leeper wrote:
Trying to install 11803 update.
OLE error 80248007
MS error codes page says "Info requested is not in data store,"
whatever that means.

Ran windows update troubleshooter.
It said "Starting bits service" ... forever.

Summary of Windows Update Troubleshooter showed no issues except
"Suggested- network reset." Don' t think that will help. I was able to
search the error code OK.

Went to services in task Manager. Right-clicked BITS, which was
stopped, selected Start. It showed "Running" for a second, then
reverted to Stopped. While I was looking at it, this same thing
happened (Update Troubleshooter started it?) I tried starting it
manually again. Again, Running then reversion to Stopped.

I found, downloaded and ran the Microsoft BITS repair tool from
https://support.microsoft.com/en-us/...ransfer-servic
This says for VISTA but also says it was Updated 04/18, so I presume
it is also for WIn10. Note: Several pages say to find this
troubleshooter from START-troubleshoot-View All. Mine has no "view
all." There is "Find and fix other problems," but nothing there for
BITS.

Running the downloaded tool resulted in "BITS repair not required
currently."


So what could be stopping it BITS?


-dan z-

The Windows Update troubleshooter should include
treatments for BITS.

Since yours goes to the running state and then stops,
that suggests the service dependencies and regsvr32 part of
it are likely OK. But maybe BITS reads some QMGR files,
it becomes upset and croaks. Just a guess.

In the script here for example:

https://www.tenforums.com/tutorials/...dows-10-a.html

del /s /q /f "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat"
del /s /q /f "%ALLUSERSPROFILE%\Microsoft\Network\Downloader\qm gr*.dat"

That's to give you some idea about the files it
might be using.

If you go to control panels in windows 10 by running

control

and select Troubleshooting, then enter "Update"
as a search term, there should be a Windows Update
troubleshooter. And in theory, it runs the same script
as the tenforums article uses. The Windows version
will stop four services (so no files are locked),
then the troubleshooter cleans out the SoftwareDistribution
folder and some other things.

And there's nothing wrong with a transient service stopping,
if there is no work for it to do. We don't know what's recorded
in qmgr* at the moment. I would expect a transient service to
run for longer than one second though.

*******

You can download an 1803 DVD and install from the DVD.
You don't even need to burn the DVD (but it doesn't hurt
to have it available as an emergency boot solution).

Once the 4+ GB ISO file is downloaded, right-click on
it and select "Mount". A virtual CD drive will appear
in File Explorer. Then, run setup.exe off the virtual CD
drive, and an Upgrade Install will start, keeping your
user files and programs. You can do an Upgrade Install
from a running Win10 OS, to take you to 1803. This assumes
there is no C:\Windows.old present on the machine at the
moment. (If there is one, remove it with cleanmgr.exe,
*not* with the trash bin!)

The reason this works, is all the necessary files are
copied from the virtual CD drive, during the current
session. When the machine reboots, the ISO mount will
be lost, but at that point, the installation process is
self-sufficient and uses information only on the hard
drive. That's why this can work.

So take your pick. Fiddle with WU and BITS until the
cows come home. Or force the issue with an 1803 ISO.
(I jammed in 1803 only a day or two after release.)

* Make sure you have a backup of C: *

That's in case something goes horribly wrong. While the
installer is very well designed, bad stuff can still
happen if the file system has latent errors in it,
and so on. The current implementation of "robust"
NTFS doesn't install confidence, when it comes to
repairing file system issues in the background.
You can easily have a file system issue that
doesn't get fixed in normal usage (and it can even
take some special new options in CHKDSK to get it
to actually fix stuff). It's for these reasons
I recommend a backup, just in case.

*******

There is at least one Powershell command which is
the equivalent of wget. It uses BITS to do a web
download. You can use that as a stimulus to test
BITS if you want. Whether the Import-Module is
required, might well depend on what OS you're running
this command on.

http://superuser.com/questions/36215...ows-powershell

(Start PowerShell, then try...)

Import-Module BitsTransfer
Start-BitsTransfer -source "http://urlToDownload"

Select a website that has a file to download in easy reach,
like http://some.com/file.txt and use that as your
urlToDownload value. It's possible "file.txt" will end
up deposited in the current working directory. And that's
a potential mechanism for proving BITS actually does stuff.

Paul

MANY thanks, Paul. You are the man.

You provided several suggestions, some of which I saw but didn't fully
understand while googling my problem. Your explanations are clear and
helpful.

It will probably be a few days before I am mentally ready to waste 24
hours trying to install a Win-10 update again, but I will let you know
how it went.

-dan z-

BTW, I did see the suggestion on deleting qmgr files on the web. I did
a file explorer search for them, and found none. Is that significant?



--
Someone who thinks logically provides
a nice contrast to the real world.
(Anonymous)

Hi Paul,
just wanted to give you an update


https://www.tenforums.com/tutorials/...dows-10-a.html

Downloaded and ran. Did get a few error messages, including no Q...
files, but BITS now stays running.


You can download an 1803 DVD and install from the DVD.
You don't even need to burn the DVD (but it doesn't hurt
to have it available as an emergency boot solution).

Wouldn't download on this Win-10 Computer (error 0x80005-0490017),
which I found is fairly common. One person said he solved it simply by
running the media creation tool on his Win-7 system and saving the iso
there. That is what I am doing, and it is downloading now.

Maybe tomorrow I'll try the upgrade. Other stuff to do today....

So far your help has been spot on.

-dan z-


--
Someone who thinks logically provides
a nice contrast to the real world.
(Anonymous)

On Sun, 10 Jun 2018 12:41:23 -0400, slate_leeper
wrote:


I ran the downloaded iso setup.exe. After a while it got to "17%
complete," so I went to do something else. Came back at 44%, still
going. Came back a few minutes later just in time to see "reverting to
previous operating system." That finished with error
0x8007042B-0x4000D, "Installation failed in Second_Boot phase with an
error in MIGRATE_DATA operation."

setuperr.log contains:

2018-06-10 20:51:02, Error SP Cannot map user hive
C:\Users\Default\NTUSER.DAT in HKEY_USERS\S-1-0-0. Error: 0x00000020

2018-06-10 20:51:02, Error CSI 0000000b (F)
STATUS_OBJECT_NAME_NOT_FOUND #1571# from
Windows::Rtl::SystemImplementation:irectRegistry Provider::SysOpenKey(flg
= 0, key = {provider=NULL, handle=0, name= ("null")}, da =
(KEY_READ|KEY_WOW64_64KEY), oa = @0xb0141eb008-OBJECT_ATTRIBUTES
{s:48; rd:NULL;
on:[147]'\Registry\Machine\{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/WINDOWS/System32/config/SOFTWARE\Microsoft\Windows
NT\CurrentVersion\ProfileList\S-1-0-0'; aOBJ_CASE_INSENSITIVE)},
disp = Invalid)[gle=0xd0000034]

2018-06-10 20:51:02, Error CSI
(F)
onecore\base\wcp\sil\ntsystem.cpp(5229): Error
STATUS_OBJECT_NAME_NOT_FOUND originated in function
Windows::Rtl::SystemImplementation:irectRegistry Provider::SysOpenKey
expression: (null)
[gle=0x80004005]

2018-06-10 20:51:02, Error CSI 0000000d (F)
STATUS_OBJECT_NAME_NOT_FOUND #1570# from
Windows::Rtl::SystemImplementation::IRtlUserProvid er::GetPathFromRegistry(...)[gle=0xd0000034]

2018-06-10 20:51:02, Error CSI 0000000e (F)
STATUS_OBJECT_NAME_NOT_FOUND #1569# from
Windows::Rtl::SystemImplementation::CUserProfile:: GetSpecialDirectoryPath(f
= 0, did = 1114112)[gle=0xd0000034]

2018-06-10 20:51:02, Error CSI 0000000f (F)
STATUS_OBJECT_NAME_NOT_FOUND #1568# from
Windows::Rtl::SystemImplementation::CUserProfile_I RtlUserProfileTearoff::GetSpecialDirectoryPath(... )[gle=0xd0000034]

2018-06-10 20:51:02, Error CSI 00000010 (F)
HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND) #1562# from
Windows::WCP::COM::CCSIExternalTransformerExecutor ::Commit(UserSID =
S-1-0-0, LoadedUserHive=(null),
LoadedUserClassesHive=HKEY_USERS\S-1-0-0_Classes,
UserProfilePath=C:\Users\Default)[gle=0x80070002]

2018-06-10 20:51:02, Error SP Failure while
calling Transformer Commit. Error: 0x80070002[gle=0x0000001f]

2018-06-10 20:51:03, Error SP UndoTransformers
failed for
C:\$WINDOWS.~BT\Sources\Rollback\MachineIndependen t\Transformers.
Error: 0x80070002


I am far from understanding any of this. Any suggestions?

-dan z-

(I am now restoring my backup image. Again.)


--
Someone who thinks logically provides
a nice contrast to the real world.
(Anonymous)

slate_leeper wrote:
On Sun, 10 Jun 2018 12:41:23 -0400, slate_leeper
wrote:


I ran the downloaded iso setup.exe. After a while it got to "17%
complete," so I went to do something else. Came back at 44%, still
going. Came back a few minutes later just in time to see "reverting to
previous operating system." That finished with error
0x8007042B-0x4000D, "Installation failed in Second_Boot phase with an
error in MIGRATE_DATA operation."

setuperr.log contains:

2018-06-10 20:51:02, Error SP Cannot map user hive
C:\Users\Default\NTUSER.DAT in HKEY_USERS\S-1-0-0. Error: 0x00000020

2018-06-10 20:51:02, Error CSI 0000000b (F)
STATUS_OBJECT_NAME_NOT_FOUND #1571# from
Windows::Rtl::SystemImplementation:irectRegistry Provider::SysOpenKey(flg
= 0, key = {provider=NULL, handle=0, name= ("null")}, da =
(KEY_READ|KEY_WOW64_64KEY), oa = @0xb0141eb008-OBJECT_ATTRIBUTES
{s:48; rd:NULL;
on:[147]'\Registry\Machine\{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/WINDOWS/System32/config/SOFTWARE\Microsoft\Windows
NT\CurrentVersion\ProfileList\S-1-0-0'; aOBJ_CASE_INSENSITIVE)},
disp = Invalid)[gle=0xd0000034]

2018-06-10 20:51:02, Error CSI
(F)
onecore\base\wcp\sil\ntsystem.cpp(5229): Error
STATUS_OBJECT_NAME_NOT_FOUND originated in function
Windows::Rtl::SystemImplementation:irectRegistry Provider::SysOpenKey
expression: (null)
[gle=0x80004005]

2018-06-10 20:51:02, Error CSI 0000000d (F)
STATUS_OBJECT_NAME_NOT_FOUND #1570# from
Windows::Rtl::SystemImplementation::IRtlUserProvid er::GetPathFromRegistry(...)[gle=0xd0000034]

2018-06-10 20:51:02, Error CSI 0000000e (F)
STATUS_OBJECT_NAME_NOT_FOUND #1569# from
Windows::Rtl::SystemImplementation::CUserProfile:: GetSpecialDirectoryPath(f
= 0, did = 1114112)[gle=0xd0000034]

2018-06-10 20:51:02, Error CSI 0000000f (F)
STATUS_OBJECT_NAME_NOT_FOUND #1568# from
Windows::Rtl::SystemImplementation::CUserProfile_I RtlUserProfileTearoff::GetSpecialDirectoryPath(... )[gle=0xd0000034]

2018-06-10 20:51:02, Error CSI 00000010 (F)
HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND) #1562# from
Windows::WCP::COM::CCSIExternalTransformerExecutor ::Commit(UserSID =
S-1-0-0, LoadedUserHive=(null),
LoadedUserClassesHive=HKEY_USERS\S-1-0-0_Classes,
UserProfilePath=C:\Users\Default)[gle=0x80070002]

2018-06-10 20:51:02, Error SP Failure while
calling Transformer Commit. Error: 0x80070002[gle=0x0000001f]

2018-06-10 20:51:03, Error SP UndoTransformers
failed for
C:\$WINDOWS.~BT\Sources\Rollback\MachineIndependen t\Transformers.
Error: 0x80070002


I am far from understanding any of this. Any suggestions?

-dan z-

(I am now restoring my backup image. Again.)



It sounds like a corrupt Default User profile (which includes
a registry file).

https://www.kapilarya.com/the-user-p...-in-windows-10

"Ron Davis

Fixed it by copying the "C:\Users\Default" folder from another PC with
windows 10 installed (VIA a flash drive). I renamed the one on my
problem machine "Default.old", then I copied the new one in.

Note: The Default folder (in C:\Users) is hidden, so you have to
click on the "view" and check "hidden files".

I then created a new user [as a test case]. Signed off my ID and
signed back on with the new user and — WOW – it worked. If you
don't have another Windows 10 PC – just checked the forums, I
saw where someone from the UK dropboxed a Default folder for
others to use for this fix. They actually had the link to the
dropbox in there comments.
"

https://helgeklein.com/blog/2013/09/...-failed-logon/

"Fixing a Corrupt Default Profile

The easiest way to fix a corrupt default profile is to delete the
content of C:\Users\Default and copy it from a working system.
Make sure, though, that the machine you copy from has the same
operating system version and language.
"

Imagine the ownership and permissions mess doing
that would cause.

In your errors above, S-1-0-0 is "Nobody", which sounds like
a Default user as much as anything. I think the Default user
is cloned when making new user accounts.

https://support.microsoft.com/en-ca/...rating-systems

SID: S-1-0-0
Name: Nobody
Description: No security principal.

This is, just a guess.

On the restored system without fixing anything, if you
created a new userid and password, logged out and
logged in as the new account, it should "fall over"
if the Default registry file is bad. And these things are
journaled too, as far as I know, so it's pretty difficult
to understand how they could be corrupted by a storage problem.
It's almost like an OS bug is causing writes to it.

Paul

I think my new motto is "1709 forever more, no more updates."

-dan z-


--
Someone who thinks logically provides
a nice contrast to the real world.
(Anonymous)

slate_leeper wrote:
I think my new motto is "1709 forever more, no more updates."

-dan z-

With backup in hand, you can experiment with it
and try and fix it.

If you don't have a tolerance for that sort of thing,
lots of people have done a clean install of the next
version, before we could suggest a second thing to
try, so there's that option :-)

Paul