Page 2 of 2

Re: Windows Update fail

Posted: Thu Aug 04, 2016 1:23 am
by vision
Top Gun wrote:...getting it to run reasonably well was a whole other story.
Thanks for sharing. Very few games run on Linux and it's video quality is horrible in general. This is one of the reasons I play Descent Rebirth so much — because there is nothing else to play!

Ok, I leave this thread now. Sorry for side convo.

Re: Windows Update fail

Posted: Thu Aug 04, 2016 8:09 am
by Jeff250
ATI/AMD video cards have always had shitty linux drivers (even shittier than their Windows drivers). If you use (or think you might ever want to use) linux, then you just don't buy that crap.

Re: Windows Update fail

Posted: Thu Aug 04, 2016 10:48 am
by Grendel
tunnelcat wrote:Foil, Holy crap! I've got 46.1 megs of cbs.persist.log files. I'll have to read your link a little bit more and see if I can deal with them.
My little server at home went from 58G free space to 72G free w/ some elbow grease :) CBS files: stop the "Windows Modules Installer" service, delete the cbs* files, restart the service.

Re: Windows Update fail

Posted: Thu Aug 04, 2016 12:00 pm
by Foil
Grendel wrote:
tunnelcat wrote:Foil, Holy crap! I've got 46.1 megs of cbs.persist.log files. I'll have to read your link a little bit more and see if I can deal with them.
My little server at home went from 58G free space to 72G free w/ some elbow grease :) CBS files: stop the "Windows Modules Installer" service, delete the cbs* files, restart the service.
Yeah, I had ~30Gb of those in one instance.

BTW, I'm betting tc meant 46.1 gigs, not "megs". The latter would be negligible. :P

Re: Windows Update fail

Posted: Thu Aug 04, 2016 2:51 pm
by Top Gun
Jeff250 wrote:ATI/AMD video cards have always had shitty linux drivers (even shittier than their Windows drivers). If you use (or think you might ever want to use) linux, then you just don't buy that crap.
To be fair, even on Windows AMD's support back then was fairly shitty. The 4670 had only been out for a couple of years, yet AMD put everything through the 4000 series on their "legacy support" cycle, where they didn't really do anything with the drivers unless there was something system-breaking.

Re: Windows Update fail

Posted: Fri Aug 05, 2016 11:12 am
by Tunnelcat
Foil wrote:
Grendel wrote:
tunnelcat wrote:Foil, Holy crap! I've got 46.1 megs of cbs.persist.log files. I'll have to read your link a little bit more and see if I can deal with them.
My little server at home went from 58G free space to 72G free w/ some elbow grease :) CBS files: stop the "Windows Modules Installer" service, delete the cbs* files, restart the service.
Yeah, I had ~30Gb of those in one instance.

BTW, I'm betting tc meant 46.1 gigs, not "megs". The latter would be negligible. :P
Oops. Fixed it Foil. I meant Gigs. :mrgreen: I also went through the process of paring those files down. I'll see what happens next time Windows Update Tuesday comes around.

Re: Windows Update fail

Posted: Sat Aug 13, 2016 2:44 pm
by Tunnelcat
OK, I want to thank Jeff250, Foil and Grendel. Between all your suggestions, it's appears to be fixed. I booted up the affected machine today and within 5 minutes, it had found all the relevant updates for August. What a difference. :)

I might just install Jeff's suggestion on my gaming rig too, because even it seems to be taking hours to find the updates, however, definitely not as long as the HP machine did. :wink:

Re: Windows Update fail

Posted: Sat Sep 17, 2016 4:08 pm
by Tunnelcat
Well, I HAD to finally install KB3172605 on both of my other Win 7 machines. Windows Update slowed to a crawl. Thanks for the help Jeff250. You helped all 3 of my Win 7 machines. :)

One other note. The installer wouldn't run if Windows Update, specifically if that one instance of svchost.exe was already running. It just put up a little window after launch that said, "searching for updates" and ran and ran and ran. I had to reboot and quickly run the installer before Windows Update went active. Then it installed OK.