You don't need to be an 'investor' to invest in Singletrack: 6 days left: 95% of target - Find out more
It happened last time, on the second of Dec, now it's done it again with 5 security updates.
Wtf?
Windows, innit.
It's most likely trampling over some other program you've installed. Is this a fairly basic Windows install or something your IT department have concocted?
Factory install with some corporate Tivoli spyware or something and PGP. However everyone else in the dept has got those things and isn't having these issues.
Just did a new Windows 7 reinstall, and while trying to set up the sound drivers for the mobo, every time I restarted the machine Windows Update decided to install some generic, doesn't-work sound driver instead, which prevented the correct one from installing. How I laughed. It didn't used to do that, either- I've done about 5 installs from these 2 discs with no problems before.
Does someone else have the same software image as you (i.e. on an identical hardware platform)? if so, ask your IT guys to clone it and install it on to yours.
Well, I could have the corporate image put on, but I don't want to. I like having my own build!
Same here. This time it was the update for the graphics card. Fotunately it was my old machine so I could get in via safe mode by banging F2 and eliminate all the batch of updates before selectively installing the updates to find which one was causing the blue screen. Six hours work.
However my new window 8 machine is now completely dead (less than a month old) and given that you need windoze to open to be able to get into the BIOS I can't think of anything better than sending it back to the manufacturer. I briefly see the name of the manufacturer and a circle going around then nothing. 🙁
Wait, you need windows open to get the bios?
And remember that selecting safe mode or whatever is not part of the bios, it's done in a split second window after the bios completes.
[quote=molgrips ]Well, I could have the corporate image put on, but I don't want to. I like having my own build!
I rest my case.
Wot?
I asked why something that works for almost everyone else doesn't work for me. It's not some weird custom black magic thing, it's just a factory build with Lenovo bloatware removed.
Shouldn't be my fault, should it? I'm bloody glad you're not in my IT dept!
So am I
And noone's suggested it's your fault cos you don't got an ipooter?
Standards are slipping
Had the same problem some time back, only way to get it to work was to install each update one at a time! Talk about reboot hell!
The problem with the old machine was a blue screen which could be avoided by going into safe mode which limits the number of drivers being used.
With the new machine I'm getting nothing and would like to be able to go into the BIOS to restore the default settings but you have to get very lucky to hit the key at the right time. We talked about this on the W8 thread, Molgrips. Anyhow for the moment I'm living with the devil I know because the way I feel about the new machine I won't resist using my splitting maul to fix it permanently.
Right, well it's now badgering me to restart to install them again - which will most likely fail.
They are mandatory security updates so I can't de-select anything.. Anyone got any ideas how best to avoid conflicts this time?
Update: (hahaha geddit?)
Ran the troubleshooting wizard, it found some problems with the update database but couldn't fix them. I had to run it again to get the exact error messages to Google, and this time it fixed all but one (background intelligent transfer service).
So restarted, and it worked. Hm.
And noone's suggested it's your fault cos you don't got an ipooter?
What did you think this was...
Windows, innit.
You can "masquer", I assume "hide" or "cover up" on an English OS, any update you want, Molgrips, even the security ones. When you get the update shield appear when you want to switch off, go into the updates manager thing, right click on the update you don't want to install and it will give you the option of hiding it.
It'd been set to automatically install, so it was too late by that point Ed.