Windows 10 Redstone 4

That CBB thing didn't work on Pro version because one of my PCs updated to latest version and wrecked it eventually, so only sure shot of disabling updates are NSudo and Wub.
I use Wub and I must use NSudo for future version to kill of updates completely.

 

@Mr. Fox @Papusan @Donald@HIDevolution @toughasnails

Can tell me why Micro$h4ft all of a sudden is trying to secretly access my webcam?

Upon Googling devicecensus.exe, it seems that it has to do with Windows update and feedback info. Fine, not a big deal, but why do they want to access my webcam for this is bey0nd me

 

I'm just updating at the moment confused , but what's the best way to stop/block this?

 

Create a rule from the Windows Firewall Advanced Menu to block all 4 locations listed below both from inbound and outbound connections:



or just buy ESET Internet Security and be done with it as it will tell you when any fishy connection is happening

 

Thanks. Interestingly enough, I only have two instances of DeviceCensus.exe, and they're only at the WinSxS folder.

 

wait till you install all Windows updates then check again

 

I've installed these a few minutes ago:

• KB4457128
• KB4456655
• KB4457146
• KB4100347

I'll be honest though, I've been updating through Settings > Update & Security > Windows Updates > Check for Updates. I should try to really do it manually next time. In any case, Windows is saying that "[I'm] up to date" already.

Here's what I got:

EDIT: I don't even know if it's important to include the one in the Temp folder to the blocked list.

EDIT 2: My results yielded the same locations from the second and third ones in your list.

EDIT 3: Added 4th update on the list from today. No new DeviceCensus.exe appeared so far.

 

Microcode forced by Micro$h4ft updates. Some info...

Microsoft re-releases Intel microcode patches for all versions of Win10
Posted on September 14th, 2018 at 07:16 woody Comment on the AskWoody Lounge
Last night, Microsoft released these new Intel microcode patches:

KB 4100347 for Win10 1803
KB 4090007 for Win10 1709
KB 4091663 for Win10 1703
KB 4091664 for Win10 1607
KB 4091666 for Win10 1507

And there’s an official Summary of Intel microcode updates. You can stop yawning now.

The updates seem to be directed at Spectre 2. Remember, we’re looking at Spectre Vn where n = 1, 2, 3, 3a, 4, and the Spectre NG series where n = 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7 and 1.8. If I read the tea leaves correctly.

Of course, Spectre (and Meltdown) don’t exist in the wild. Many people feel that the chances of them ever appearing are very slim because it’d take a whole lot of work to get them going and parse the incoming data.

Those of you who run servers with multiple users and sensitive data might be concerned. The rest of us… Meh.



UPDATE: Günter Born has a great exploration of the patches, WSUS, and a Microsoft bot on his Born City blog.


Windows Patches/Security KB 4090007, KB 4091663, KB 4091664, KB 4091666, KB 4100347

----------------------------------

Windows 10: Microcode updates (09/13/2018) & WSUS chaos borncity.com | Posted on 2018-09-14

Note: After the installation of the microcode update KB4100347 my Windows 10 V1803 test machine appears to be much slower. It took 10 – 20 seconds after selecting Settings – Update & Security – Update until the right column of the settings page was filled with content. It improved after some time, but the machine feels slower. Also this update for Intel CPU flaws seems to be delivered again also to AMD systems ( see this German post).

Windows 10 users as guinea pigs?
While writing the blog post, I was thinking about whether the Windows 10 users on the clients should serve as guinea pigs. Why?

• According to Microsoft, the microcode updates should not be offered via WSUS, but they are still distributed and installed via Windows Update.
• However, Windows 7/8.1 usually does not get these microcode updates, only Windows 10 is getting updates.
• And on Windows server systems, the administrator must explicitly activate the microcode updates (due to performance problems) via the registry entry.

This makes me wonder about the relevance and importance of these microcode updates against Spectre and Meltdown. I don’t know an attack scenario used ‘in the wild’, which exploits the vulnerabilities. Moreover, the microcode updates makes machines extremely slow – and comes often with trouble on top (some updates are then withdrawn). Also my impression ist, that Apple’s macOS don’t receive patch in that frequency. Or how do you see it?

 

Thanks for the heads up Poopoosan, and I was wondering why my taptop feels sluggish

I uninstalled the Microcode update, restarted, then hid the update

 

I can make it look more nasty!

Intel microcode updates from the Redmond Morons... KB 4100347 for Win10 1803,
Windows Server version 1803 - Microcode for Coffee lake... 13.09.2018


Intel microcode updates from the Redmond Morons... KB4346084 for Win10 1803, Windows Server version 1803 - Microcode for Coffee lake... 20.08.2018


AS YOU CAN SEE IT'S A HUGE MESS!! @Phoenix @Mr. Fox Puke with me?

LATEST microcode revision guidance.PDF August 8, 2018 From INTEL


What will you pick of those?

 

But isn't your BIOS updated to latest version w/ Spectre fixes and Why MSFT pushed a uCode patch when its already patched?
By default OS should ignore the OS level uCode when it checks your BIOS.
Thanks for the detailed screenshot with KB Article.

Aren't they same? Usually I had better luck with disabling Microsoft Spectre protection to get the speedup. Even on Linux w/ retpo things are slowing on older hardware making it unusable. As a matter of fact, the same ucode works beautifully on older hardware at startup and as apps get loaded hardware chokes making it worse than Linux. I'm scratching my head on how could this happen?

 

Of course shouldn't Win update force microcode patches on your pc. @Phoenix should have microcode 0x96 if he is on latest bios. Maybe even with the one before the last one.

Look on the pict I posted or click each KB and see what they offer...

 

I restored back the BIOS from MSI after Windows update updated my BIOS

 

You find what microcode version you have in Hwinfo summary. Check it out.

 

how? have you a step by step guide?

 

Fire up Hwinfo. Right click icon and chose settings. Check the yellow box. Close and save. Next time you run Hwinfo check the box "summary only" then run.




Close Hwinfo. Fire up again go into settings and remove the checkmark in yellow as above. Click sensor only box. Run

 

I have Microwave Update revision 84

Is that good or it has cancer?

 

If you diabled everything of protection in InSpectre it doesn't matter.

 

When I choose to disable Spectre and Meltdown, nothing happens, yet it still says performance is good. what gives?

 

The tab doesn't switch color while you put mouse over? Aka you can click on it. Totally locked?

 

nope, the program is buggy, I have not any color changes.

 

See if it changes if you try Intel microcode update KB4346084 for Win10 1803. Should launch 0x96

 

Now it shows this:
jpeg upload

Clicking disable does nothing. this app hasn't been updated in ages so I wouldn't touch it anymore

 

Lovely and you run the patch with 0x96 who is Intels latest microcode. Nice. The tool work for me.

Edit. If you haven't saved previous versions https://web.archive.org/web/*/https://www.grc.com/inspectre.htm

 

Can you export the reg keys for that. You're damn lucky that it is indeed a bug and isn't applying any protections!
Please export the reg keys you find in locations mentioned in the link https://support.microsoft.com/en-in...ive-execution-side-channel-vulnerabilities-in
I'll try it in my sis's PC which was wrecked by W10. She has exams now which is perfect time for testing OR on my older PCs.

 

InSpectre works fine. You have to run it as admin, clicking the buttons just set a few registry values, so Windows disables the OS based Meltdown Protection or the Spectre based MC protection. You have to reboot of course. After reboot, the colors change to red (not protected). Spectre protection just works with MC, Meltdown is unrelated to MC. "MC update available" font will stay green if your system has one loaded.

 

I'm gonna have to get a course on InSpectre because I didn't really bother learning about it before.

Anyway, I'm not sure if it was wrong to update today with KB4464218 (OS Build 17134.286).

I need to learn how you guys check and know what cancer looks like.

 

Windows 10 Cumulative Update Build 1803 (17134.286)

http://download.windowsupdate.com/c..._ab91d3d8387a870fc4eb5f9bcd2d6d08afac0339.msu

Changelog

 

Don't update it, it screwed my network up and WUMT Wrapper Script I always use

 

I did, it screwed nothing

 

Exactly. Have never ever seen it. Not with any of the previous WinScrew Update patches.

 

Where is Mr. Phoenix? I think latest update wrecked my Bluetooth FTP/A2DP on windows OS. On my android and iOS it works flawlessly. On Wp when I disconnect BT audio, the phone forces to connect to PC. It seems everything is forced on Microsoft phone/desktop OS. On linux, everything is fine.
Anyway I'll do a MR image and apply the update.
I saw there are BT driver update for killer 1535 10.0.714. https://www.catalog.update.microsoft.com/Search.aspx?q=qca61x4

 

Windows 10 September 20, 2018 Cumulative Update—KB4458469 (OS Build 17134.319)

Microsoft has lost its mind, 3 cumulative updates in one week, this is one buggy OS man

September 20, 2018—KB4458469 (OS Build 17134.319)

Download =

http://download.windowsupdate.com/d..._22139e5b137440eac5526d4c5c85762fcbe80030.msu

Changelog:

https://support.microsoft.com/en-us/help/4458469/windows-10-update-kb4458469

 

This os ain’t for people with ****y internet download speed or expensive mobile WiFi. And within 1 month we have new version with more of the same. Maybe even worse

 

I'm waiting for 3 more days until 4xx series comes up as a Diwali gift.!