Read more.Because such systems may otherwise face "a UEFI screen reboot or crash repeatedly".
Read more.Because such systems may otherwise face "a UEFI screen reboot or crash repeatedly".
Spooky hidden low level Intel software?Originally Posted by Hexus
Spooky high level Microsoft software.
I'd be more worried about everything reverting to English (US) so the new "features" work and when you change it back then it's like nothing really has changed
Old puter - still good enuff till I save some pennies!
Eeek. I've got an Intel 750 PCIe drive as my OS drive. Got the update yesterday and so far it looks to be ok *touching every piece of wood available*.
Millennium (09-05-2018)
Oh great! The update auto installed the other day on an Intel SSD. Glad Micro$oft tested before rolling it out and forcing the update on us. I've got all privacy settings turned on and still get forced to do the update. I did get a couple of BSOD the other day, but can't remember if it was before or after the update, at the time I assumed it was due to my wireless headphone being plugged in to charge... oh well, fingers crossed nothing else goes wrong.
Millennium (09-05-2018)
Did Hexus choose a thumbnail of a newer drive (900P) that has NO issue? or no?
I think Hexus used the same image that the original report did, if you'd read any of them, you'd know that Intel/MS have left us all guessing which drives/series are currently affected.
Why did my brain read the title as "April fools update" !?
I'm seeing one (1) Intel 600P owner reporting temperature issues on W10 1803; 1709 normally 25-30 degrees, with 1803 55-60 degrees (I assume Celsius). He rolled back and set the update to Semi Annual channel w/40 days delay.
And that is one of the reasons (though not the only one) why I refused, and still refuse, to migrate from W7 to W10. If I don't have control over when, and indeed what, updates occur then I no longer control my own PC, and I never know when an 'update' is going to kill something on my PC, and as I rely on some quite old software snd hardware, it could kill something fundamentally important.
And that is a risk that, for me, is unacceptable.
To be fair Saracen we don't have much control over what updates get installed on Windows 7 either these days, since Microsoft in their infinite wisdom decided to roll most updates into single patches the "what" it fixes part is normally a standard boilerplate, about the only control we have is when something something gets patched.
In my eyes Microsoft have basically turned themselves into a inferior amalgam of Apple and Google.
Beg to differ here. I have full control of updates in Win7 , I never update it from installation. First thing I do is turn Windows update off in MSconfig as soon as I've installed before anything else. Anti-Virus and CCCleaner loaded before anything else after that and never had a problem in all my years without Windows updates bloating my O/S. Win 10 is an ever spiralling mess. which I will not be forced into.
I didn't say we don't have control over when the updates are installed just what is installed, i.e since they started doing monthly quality security quality update security monthly or whatever the hell they call them we no longer have control over what gets patched and what doesn't, it's a case of choosing whether to install something with scant information on what exactly you're installing.
I have full control over my Windows updates because I physically went to the effort to turn off all the switches using registry changes and local policy settings. I review them every time I update.
Considering some people here go through far more effort for far smaller things, I'm surprised that's a problem.
There are currently 1 users browsing this thread. (0 members and 1 guests)