knuttle wrote:
On 8/21/2015 9:00 PM, Paul wrote:
Keith Nuttle wrote:
I had to reinstall every thing after trying Windows 10. I made it
through the 155+ updates to Windows 8, installed Windows 8.1,and most
of its updates.

The updates and it appears downloads from the Windows store is no
longer working.

I checked and see I am getting repeated occurrence is of this error.

Since I tried repeatedly to install the updates, I thought it could be
the problem. Can some one help'

"The server {4991D34B-80A1-4291-83B6-3328366B9097} did not register
with DCOM within the required timeout."

Your Background Intelligent Transfer Service (BITS)
is not starting in time. DCOM is apparently part of
the trigger for contacting it or something. Googling
with BITS and that string of digits should show
you all sorts of examples.

http://smallvoid.com/article/winnt-services-bits.html

BITS is used by Windows Update, so you could look
for a TroubleShooter for Windows Updates in the
Control Panels. If you were running an OS like
WinXP, you'd have to look for a Microsoft Fixit,
which is a Troubleshooter for the WinXP era.

You might also look for CBS.log, as that might
be used for logging. Not sure. I don't know if te
Windows Store keeps a separate log. The Windows
Store (on Win10), has "wsreset.exe" for fixing
Windows Store problems, and as far as I know,
all that it does is delete the contents of the
Windows Store cache.

Paul
The links from the above URL are all for version of Windows before 8.

Will this apply to Windows 8.1?

BITS has existed since WinXP. So some of this
stuff, the approach has been consistent for
a while. Start by checking for a "Troubleshooter"
item in Control Panels, and see what's there.

(On WinXP, troubleshooting exists in the form
of "Fixit" files, which used to be contained on
the MATS web page. For example, the Upperfilter
problem with optical drives, there was a WinXP
Fixit for that. Whereas now, you would look
in the Troubleshooter control panel for it.)

And note that some services on Windows, are demand
based. The service will not be running normally.
A function in Windows wants the service, and
it is triggered on demand. The service remains
running for as long as it has work to do. About
five seconds later, it self-terminates. This can
cause anguish for end-users who think they can
manually start a service and solve all of their
problems, as five seconds later the service
can be gone again. (Some services have been known
to auto-terminate, but with a longer time constant.)

If there is a race condition in the software (because
of the transient nature of this sort of service), it's
going to be difficult to watch it with ordinary tools
and see what is going on.

You can use Process Explorer from Sysinternals, but
by the time you click on a svchost and verify that
BITS is inside it, it could be gone again :-)

*******

There are many similarities between the Vista+ versions
of OS. The guy who runs the sevenforums.com, eightforums.com
and tenforums.com site, gets to copy many of the
tutorials from one site to the next. Where this
doesn't always work out, is for the things
that Microsoft broke. Such as the on-again,
off-again, Windows 7 system image (backup)
capability. Or the Refresh and Reset features
which get broken, and I can't keep track of
how they work, whether they still work, whether
the user must prepare a custom image for it
to work and so on. So some of the features,
would need a lot of documentation effort and
testing, to keep the website advice up to date.
But for the more regular stuff, the advice
can remain the same from OS to OS.

Paul