A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows 8 » Windows 8 Help Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Update errors



 
 
Thread Tools Rate Thread Display Modes
  #1  
Old August 21st 15, 08:36 PM posted to alt.comp.os.windows-8
Keith Nuttle
external usenet poster
 
Posts: 1,844
Default Update errors

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."
Ads
  #2  
Old August 22nd 15, 02:00 AM posted to alt.comp.os.windows-8
Paul
external usenet poster
 
Posts: 18,275
Default Update errors

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
  #3  
Old August 22nd 15, 02:22 AM posted to alt.comp.os.windows-8
. . .winston[_2_]
external usenet poster
 
Posts: 404
Default Update errors

Keith Nuttle wrote on 08/21/2015 3:36 PM:
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."



As noted previously their is no need to install 8.0, update Windows 8.0,
install 8.1, etc..

Just use the Windows 8.1 Media Creation Tool created media.
- it accepts both Win8.0 and 8.1 product keys, installs 8.1,
thereafter update 8.1 via Windows Update.



--
...winston
msft mvp windows experience
  #4  
Old August 22nd 15, 12:18 PM posted to alt.comp.os.windows-8
Keith Nuttle
external usenet poster
 
Posts: 1,844
Default Update errors

On 8/21/2015 9:22 PM, . . .winston wrote:
Keith Nuttle wrote on 08/21/2015 3:36 PM:
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."



As noted previously their is no need to install 8.0, update Windows 8.0,
install 8.1, etc..

Just use the Windows 8.1 Media Creation Tool created media.
- it accepts both Win8.0 and 8.1 product keys, installs 8.1,
thereafter update 8.1 via Windows Update.



I did not have a choice. When I rolled back from Windows 10, it rolled
back to the OEM Windows 8.
  #5  
Old August 22nd 15, 01:20 PM posted to alt.comp.os.windows-8
knuttle
external usenet poster
 
Posts: 262
Default Update errors

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?
  #6  
Old August 22nd 15, 03:37 PM posted to alt.comp.os.windows-8
Paul
external usenet poster
 
Posts: 18,275
Default Update errors

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
  #7  
Old August 22nd 15, 07:06 PM posted to alt.comp.os.windows-8
. . .winston[_2_]
external usenet poster
 
Posts: 404
Default Update errors

Keith Nuttle wrote on 08/22/2015 7:18 AM:
On 8/21/2015 9:22 PM, . . .winston wrote:
Keith Nuttle wrote on 08/21/2015 3:36 PM:
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."



As noted previously their is no need to install 8.0, update Windows 8.0,
install 8.1, etc..

Just use the Windows 8.1 Media Creation Tool created media.
- it accepts both Win8.0 and 8.1 product keys, installs 8.1,
thereafter update 8.1 via Windows Update.



I did not have a choice. When I rolled back from Windows 10, it rolled
back to the OEM Windows 8.


If it rolled back to 8.0, the using the 8.1 media can be used to update
8.0 to 8.1 avoiding the need to install the 155 Win 8.0 updates.

--
...winston
msft mvp windows experience
  #8  
Old August 23rd 15, 01:56 PM posted to alt.comp.os.windows-8
Keith Nuttle
external usenet poster
 
Posts: 1,844
Default Update errors What next

On 8/21/2015 3:36 PM, 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."


It has been a week since I had to rollback Windows 10 after it was
locking up the computer to Window 8. As I have said the roll back put
me at the OEM OS and I had to reinstall all of the updates, AND then
install Windows 8.1. Things are still not back to normal

The update system is broken. I have tried everything that has been
posted and and all of the suggestions on the sites provided except
exporting parts of the registery to fix the problem. (I do not have
access to another 64 bit computer.)

Most recently I downloaded WindowsUpdateDiagnostic.diagcab. and ran it.
When I tried the individual option, after over a half an hour they
never completed. On the third try I ran the advance option, and it did
finish but had errors after appearing to down load a couple of files.
(as see in the task manager Disk activity not in the Internet activity )

Right now the update facility is not working and it looks like my only
option is to back up all of my data, use the Toshiba reinstall the OEM
Windows 8 on a cleaned disk and start over. This time as has been
suggested I will use the Install tool to install Windows 8.1.

I guess there is a second option that is to live with a broken computer
and not have Solataire.

Is there any thing else I can do short of the start over option?
  #9  
Old August 23rd 15, 04:57 PM posted to alt.comp.os.windows-8
Paul
external usenet poster
 
Posts: 18,275
Default Update errors What next

Keith Nuttle wrote:
On 8/21/2015 3:36 PM, 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."


It has been a week since I had to rollback Windows 10 after it was
locking up the computer to Window 8. As I have said the roll back put
me at the OEM OS and I had to reinstall all of the updates, AND then
install Windows 8.1. Things are still not back to normal

The update system is broken. I have tried everything that has been
posted and and all of the suggestions on the sites provided except
exporting parts of the registery to fix the problem. (I do not have
access to another 64 bit computer.)

Most recently I downloaded WindowsUpdateDiagnostic.diagcab. and ran it.
When I tried the individual option, after over a half an hour they
never completed. On the third try I ran the advance option, and it did
finish but had errors after appearing to down load a couple of files.
(as see in the task manager Disk activity not in the Internet activity )

Right now the update facility is not working and it looks like my only
option is to back up all of my data, use the Toshiba reinstall the OEM
Windows 8 on a cleaned disk and start over. This time as has been
suggested I will use the Install tool to install Windows 8.1.

I guess there is a second option that is to live with a broken computer
and not have Solataire.

Is there any thing else I can do short of the start over option?


Go to the Troubleshooting control panel. Type "Update" in
the search box in the upper right hand corner of Troubleshooting.
That would give the built-in version of diagcab for Windows Update.

The basic recipe for Windows Update is pretty simple. Turn off
two services. Now that nothing owns SoftwareDistribution folder
clean it out and start again. Turn the two services back on.
When Windows Update is run by the user, the SoftwareDistribution
state information will be regenerated.

For a free copy of Solitaire from the MicrosoftStore (versus
porting one from a previous OS), the Windows Store subsystem
has to be working. AFAIK, it shares BITS subsystem with
Windows Update, but I could be wrong. And the tool for
cleaning the cache used by WindowsStore is "wsreset.exe".

"When WSReset.exe runs, it will open the Windows Store app.
The Windows Store app screen will reset a couple times
while the tool is emptying the app's cache and then it's
done. It's a quick process."

Could you have some permissions problems these tools
can't fix ? Quite possible. Microsoft repair tools
don't seem to deal with complicated situations, and
assume a benign rather than a hostile environment.
There's no reason for the tool to consider
a permission could be set wrongly. And no,
smashing everything with TakeOwn, doesn't
solve a problem (necessarily) where
TrustedInstaller is supposed to be
the owner.

Have a look for log files, such as WindowsUpdate.log
or cbs.log. Or even Event Viewer. There is a one-liner
for cleaning out Event Viewer, but of course that
also removes useful history a diagnostician might
need. As hard to believe as that might be (that
anyone could stomach the interface long enough
to spot a problem).

(Event Viewer cleaning recipe, one-liner for powershell)
http://jpwaldin.com/blog/?p=166

(To be run in an Administrator powershell.exe window)

wevtutil el | Foreach-Object {wevtutil cl "$_"}

And because I can't keep all the logs in my head,
I sometimes use Agent Ransack, look for all log
files, and sort them by date. Then, if I've been
messing with a subsystem, the theory is that the
associated log has the latest date stamp. And that's
how I figure out what log might be the one to consult.

HTH,
Paul
 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 06:45 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.