funny thing.. it would seem enabling core integrity stops kaspersky from using its own hardware virtualization based protection.

i mean.. i haven't seen that particular warning before in kaspersky...

thanks for that..
removed the 2 things from driver store..
had to go back to autoruns to actually delete the aicharger from autorun (unticking it not enough) and the core thingy was turned on......

have a similar issue. mine has usb2ser.sys as well as 2 other drivers (some wireless xbox 360 controller xusb21.sys and asus aichargerplus.sys)
of the 3, only aicharger has an entry in autoruns...

bit of an odd question. i was using cpuz to see which microcode i have and noticed this bit..
IBRS supported, disabled
IBPB supported
STIBP supported, disabled
inspectre says i'm protected...

what kind of info on the last scan were you looking for?
click on virus & threat protection -> threat history and there's a bit at the bottom saying when the last scan was. chances are it's quick...

yes, but all your autofills/pw remembered tracks from normal to incognito (and variants). nothing to do with cookies or temp files.

take firefox. open an incognito page and you can still see all...

surely your biggest problem is having saved the logins and stuff under normal mode (or any mode for that matter!)? if you delete those, then surely it won't be autofilled?

i think incognito mode...

odd thing is... ever since upping to 1803, windows stopped me from doing that. "your it admin has limited access.. blah blah" (i do have 3rd party av installed.. but don't see why that should stop...

weird thing is.. it keeps referencing to the changes dated back to may 1

any idea why i keep (every few days? week?) getting a notification in 1803 saying "we've updated our terms of use"?

in the past year intel has released bios security fix in the following order: imei -> spectre -> sfi (edit... whoops.. that was meant to be SPI)

when your mb maker will release bios that include...

poor wording doesn't even begin to describe the screen showing the frequency option locked as "automatically (recommended)"

thanks for the fix.

in 1803, the pulldown menu is locked as it thinks we are in the insider program (obviously we ain't).
in the registry, i already have NumberOfSIUFInPeriod set as 0. there's no existing entry for...

i have a weird variation.

sometimes when cold booting, the monitor doesn't "wake up". there's no internal speaker, so no warning to diagnose. holding the power off/shut down button on the machine...

i didn't even realise anything was blurry. was playing something fullscreen at 1080 (desktop is 4k, 200%) and win10 bounces up a notification asking me if i want to fix the blurring. you got a choice...

core isolation was on for me without me doing a thing i think and i use kis. is vt-d and stuff enabled in your bios?
i do notice that i cannot scan a selected file with defender from right click...

why on earth would nvidia need java? i didn't even need to reinstall the drivers for 970 after my upgrade.
for nvidia, i normally only select vid, audio and physx bits and ditch the rest

what...

what do those plugins do precisely?

ps.. it's back to redirecting again today XD think it's something on google's end.

pps.. and just like that it's stopped redirecting.. someone at google...

kaspersky internet security.
it's odd, because i just had a look at a relative's crappy laptop that uses the same kaspersky as well and it had the normal screen... though that was before i updated...

odd question. i use win10 home 1709 (with all updates) + 3rd party security suite and my screen looks different. when i hit app& browser control-> exploit protection settings, the page just says...

oddly enough.. that's not the case anymore this morning.. (so far anyway)..

or rather... as before it opens up in new tab (eg.. searching bbc)...

bit of an odd question. when using firefox, i search (google by default) with the old separate search box. noticed today (or last day or 2?) that it opens the results in a new tab (which is normal),...

yeah, really puzzled me why they didn't do it via os in the 1st place. linux did it, though they did pull it after by "updating" to the older microcode under newer version name.

i imagine you need...

it really depends on what up to date bios means. has any mb makers updated their bios to the latest micro code updates intel released recently yet? (ie.. not the initial ones that got pulled). i know...

how weird. re-reading the .192 and .125 notes makes me think it's just an old issue not resolved.. (that is.. an error showing up when there's no actual error). i guess if everything else works.....