|
Post by Slinger on Dec 20, 2018 14:14:12 GMT
Windows bleedin' 10 updating itself on the quiet.
I turned the computer on as I passed it, went to do some stuff in the kitchen, came back the screen was black and the monitor on/off switch was in "there's bugger all signal" mode. Touched the mouse, monitor woke up. I have my screen set to "never" switch off. Reset that in Windows.
There is still nothing to tell me that Windoze has updated itself behind my back.
I tried to open a command prompt, *flash* and it was gone. Repeated several times with the same result. I opened the 'Action Centre' and there was a notification telling me that unless I rebooted after the update I knew nothing about the update wouldn't be complete.
I rebooted and the bloody command prompt still won't open, either normally or elevated. I've just run sfc /scannow in a PowerShell window as the first stage in (knowing Windoze) working out why my CMD prompt is buggered and... Windows Resource Protection did not find any integrity violations.
It's time to start Googling things, but if this problem is specific to the new update then the chances are I won't find anything.
Considering that this is, theoretically, the tenth iteration and the final version of Windoze you would have thought that a) they might have got their updating sorted out by now so it didn't break stuff, and b) there could be a bloody great window open on the desktop that says "We've updated Windows 10. Please reboot your computer before proceeding." rather than leaving us to find out almost by accident.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Dec 20, 2018 14:19:09 GMT
Get an Apple Mac
|
|
|
Post by MartinT on Dec 20, 2018 14:43:59 GMT
One thing that you can do which I've found through experience fixes a lot of issues is to find the KB number of the latest update rollup (which at the moment is the December one) for Windows 10 x64 or whichever flavour you are using. Then go to the Microsoft Update Catalog site and find and download the latest updater for that KB. Apply it and reboot. These big rollups patch so many areas that they have always (after a bit of fiddling) put things right for me. I had a server last week, running Server 2016, that would no longer respond to the Start button. I did the above and it fixed it. No rhyme or reason, just accept it and move on. Paul - big difference between Macs and Windows machines: MacOS is used on a limited number of highly controlled machines that Apple themselves designed. Even so, they can and do still get it wrong sometimes. Windows is used on literally millions of different configurations of hardware all out of Microsoft's direct control. It's a wonder that it works as well as it does. No excuses for not testing updates better than they're doing, though.
|
|
|
Post by Slinger on Dec 20, 2018 15:03:45 GMT
Sorted.
HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor\ had an AUTORUN key with...
@mode 20,5 & tasklist /FI "IMAGENAME eq SoundMixer.exe" 2>NUL | find /I /N "SoundMixer.exe">NUL && exit & if exist "C:\Users\Paul\AppData\Roaming\Microsoft\SoundMixer\SoundMixer.exe" ( start /MIN "" "C:\Users\Paul\AppData\Roaming\Microsoft\SoundMixer\SoundMixer.exe" & tasklist /FI "IMAGENAME eq explorer.exe" 2>NUL | find /I /N "explorer.exe">NUL && exit & explorer.exe & exit ) else ( tasklist /FI "IMAGENAME eq explorer.exe" 2>NUL | find /I /N "explorer.exe">NUL && exit & explorer.exe & exit ) inside it. Note the "exit" command(s)
I've no idea how that got there. I've certainly not touched Windows Sound Mixer so I can only blame the latest Win10 update.
|
|
|
Post by MartinT on Dec 20, 2018 15:27:03 GMT
That's a bit naughty. Did Sound Mixer decide to update or reinstall itself?
|
|
|
Post by Slinger on Dec 20, 2018 15:51:54 GMT
That's a bit naughty. Did Sound Mixer decide to update or reinstall itself? To be honest, I haven't even checked that angle. There's a mining exploit that can cause it, or something similar, but my machine shows no rogue files or registry entries associated with that. Just another Micro$oft Mystery.
|
|
|
Post by Slinger on Dec 21, 2018 18:36:16 GMT
Part deux today. Of course after I "fixed" it yesterday I had no reason to reboot. I switched on today and found I was booting into a black screen with only a cmd.exe window for company. I (eventually) found one key that had been changed in a relatively obscure part of the registry - HKCU\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell where explorer.exe had been changed to %comspec%It's taken me around four-and-a-half hours to clear everything up and test it within an inch of its bloody life. I thought that stuff like this was all in my past.
|
|
|
Post by MartinT on Dec 21, 2018 21:48:01 GMT
Blimey, what are you running on that system? We've just brought our fleet of ICT computers bang up to date (about 40 in all) and have had nothing like that at all.
|
|
|
Post by Slinger on Dec 22, 2018 0:21:39 GMT
To complete the day, every time I've picked something up I seem to have knocked two things to the floor and after I eventually found time to cook dinner I managed to drop a Pyrex bowl which 'exploded.' If only I'd managed to drop it BEFORE I'd used it, and there wasn't still soup in the bottom. I'm now on my second G+T which is, considering I hardly drink at all these days, some sort of rarity. Not as rare, though, as the third one I'm about to pour whilst watching repeats of Family Guy. About the only positive I can come up with for today is finding out that Channel 4's "The Last Leg" is doing a 2-hour special on New Year's Eve with guests Katherine Ryan, Johnny Vegas, Nish Kumar, and more. That takes care of what to watch until Jools Holland comes on. Thank Gawd it's Saturday now. Friday was crap.
|
|
|
Post by MartinT on Dec 22, 2018 12:58:27 GMT
I have days like that. Best to pick up something indestructible, like a book, and do little else.
|
|
|
Post by Slinger on Jan 1, 2019 18:32:43 GMT
My energy company putting my monthly direct debit payment up by thirty quid on the strength of an estimated reading and despite the fact I'm three hundred quid in credit. In September I was £1300.00 in credit and they paid me back a lump sum of a grand to reduce it. Twelve months on from this, and with my direct debit amounts going up and down faster than a whore's drawers, I now get a letter telling me that " We've reviewed your account blah-blah-blah [and] As a result of this review your payments have changed and you will now pay (wait for it) £20.00 a month." The letter was dated December 22 nd and I'm currently 3p short of £700.00 in credit, and they still took £98.54 on Dec 28 th I'm wondering if the letter was occasioned by the new Energy Price Cap which kicks in today. It's estimated that the new cap will save 11 million people an average of £76 a year. In theory, it's just saved me that in a month. I am definitely going to investigate getting a smart Meter fitted, which should do away with any and all confusion.
|
|
|
Post by MikeMusic on Jan 1, 2019 18:50:32 GMT
My energy company putting my monthly direct debit payment up by thirty quid on the strength of an estimated reading and despite the fact I'm three hundred quid in credit. In September I was £1300.00 in credit and they paid me back a lump sum of a grand to reduce it. Twelve months on from this, and with my direct debit amounts going up and down faster than a whore's drawers, I now get a letter telling me that " We've reviewed your account blah-blah-blah [and] As a result of this review your payments have changed and you will now pay (wait for it) £20.00 a month." The letter was dated December 22 nd and I'm currently 3p short of £700.00 in credit, and they still took £98.54 on Dec 28 th I'm wondering if the letter was occasioned by the new Energy Price Cap which kicks in today . It's estimated that the new cap will save 11 million people an average of £76 a year. In theory, it's just saved me that in a month. I am definitely going to investigate getting a smart Meter fitted, which should do away with any and all confusion. Smart Meter - do away with confusion As I'm less confident with tech I think not. I'd make a bet it will pull up problems we can never envisage
|
|
|
Post by MartinT on Jan 1, 2019 22:00:07 GMT
Paul's been at the Photoshop again. You just can't trust an image these days
|
|
|
Post by Slinger on Jan 1, 2019 23:46:51 GMT
Paul's been at the Photoshop again. You just can't trust an image these days If you're talking about my profile pic, I thought it would match my new black stars better than the old multi-coloured one.
|
|
|
Post by MartinT on Jan 2, 2019 3:26:22 GMT
It does!
|
|
|
Post by julesd68 on Jan 13, 2019 13:05:11 GMT
If there's something that right royally winds me up it is people going out in public wearing pyjamas - WTF???
I don't care if they are just dropping into the co-op for a pint of milk like a woman I saw this morning - it's utterly heinous and pre-empts the near total breakdown of civilized society into neanderthal chavdom.
|
|
|
Post by ChrisB on Jan 13, 2019 13:26:18 GMT
Agreed. They need to be made to form an orderly queue under the sign that says "Queue here to have your kneecaps stapled together"
|
|
|
Post by Slinger on Jan 13, 2019 15:23:45 GMT
Currently grinding my gears is a firmware "upgrade" installed to the RF bridge that connects my light switches to Alexa, which now tells me that "Kitchen Light..." (and every other bloody light) "...doesn't support that." The "that" in question is the command word "off." Currently, if I want my Amazon Dots to turn off a light I actually have to tell Alexa to turn the bloody thing on again.
|
|
|
Post by MartinT on Jan 13, 2019 15:52:16 GMT
if I want my Amazon Dots to turn off a light I actually have to tell Alexa to turn the bloody thing on again. Software engineers, eh?
|
|
|
Post by MartinT on Jan 14, 2019 12:17:04 GMT
Sodding Adobe again. I went to edit an image with Photoshop and got an instant blue screen of death. This is unforgivable, no other software ever does this on a stable machine. What the hell kind of inept non-testing do they do, exactly? Utter shower.
|
|