Windows Enterprise administrators will get full control over driver and firmware updates - gHacks Tech News

Windows Enterprise administrators will get full control over driver and firmware updates

Microsoft unveiled a new deployment service for driver and firmware updates on Windows devices during the 2021 Ignite conference. A video presentation and Tech Community article have been published, which inform administrators and interested end users about the upcoming service changes.

The main takeaway is that administrators will get more control over driver and firmware updates.

Nir Froimovici, Microsoft Principal Program Manager Lead, begins the introduction with an overview of the current situation for administrators when it comes to deploying updates and new firmware versions.

Driver and firmware updates are released regularly, for instance to address issues or patch security flaws, and most of these drivers are released via Windows Update.

Intune and Configuration Manager administrators face different issues when it comes to driver and firmware updates. The former have access to policies that allow or deny all drivers on devices from Windows Updates, but no option to allow drivers only after administrative inspection according to Froimovici.

Configuration Manager administrators on the other hand cannot sync drivers from Windows Updates with WSUS. Microsoft notes that many administrators tend to delay driver servicing until enforced, which usually happens during operating system upgrades.

microsoft windows it admins driver firmware updates

The new commercial deployment service for drivers & firmware is "coming to Intune and Microsoft Graph in the second half of 2021" according to Microsoft. A private preview will be launched in March 2021.

Configuration Manager administrators will benefit from the introduction of the new service, without changing the way they "service Windows updates with WSUS".

When our Private Preview launches, co-management will support configuring a cloud scan for drivers only, knowing that Windows Update will offer only those drivers you approved and at the time you scheduled them. There will be no change to any of your deployments from WSUS.

Intune administrators will get full control over new drivers and firmware once these become available, which gives them options to react to these before the new drivers or firmware are installed on user devices.

Admins can review available content and then make approval decisions on a per driver basis – no longer all and any drivers are offered by default – and choose the timing when Windows Update should start offering the driver to the devices in the policy.

Administrators may view the full Ingite 2021 session for an in-depth look at the new capabilities.

Now You: how do you handle driver and firmware updates? (via Born)

Summary
Windows Enterprise administrators will get full control over driver and firmware updates
Article Name
Windows Enterprise administrators will get full control over driver and firmware updates
Description
Microsoft unveiled a new deployment service for driver and firmware updates on Windows devices during the 2021 Ignite conference.
Author
Publisher
Ghacks Technology News
Logo
Advertisement

Previous Post: «
Next Post: »

Comments

  1. Tired Bastard said on March 8, 2021 at 6:03 pm
    Reply

    Having M$ Winblows in charge of firmware updates is UTTERLY INSANE!

    Those machines wont last long.

  2. Anon7 said on March 8, 2021 at 6:50 pm
    Reply

    Will they get full control over this amount of telemetry/data gathering?

    This is the telemetry that win 10 collects that you can not turn off in its setting.

    0.0.0.0m.hotmail.com

    0.0.0.0apps.skype.com

    0.0.0.0pricelist.skype.com

    0.0.0.0ui.skype.com

    0.0.0.0wes.df.telemetry.microsoft.com

    0.0.0.0watson.telemetry.microsoft.com.nsatc.net

    0.0.0.0watson.telemetry.microsoft.com

    0.0.0.0watson.ppe.telemetry.microsoft.com

    0.0.0.0watson.microsoft.com

    0.0.0.0view.atdmt.com

    0.0.0.0survey.watson.microsoft.com

    0.0.0.0statsfe2.update.microsoft.com.akadns.net

    0.0.0.0s0.2mdn.net

    0.0.0.0fe2.update.microsoft.com.akadns.net

    0.0.0.0www.msftncsi.com

    0.0.0.0www.go.microsoft.akadns.net

    0.0.0.0www.bingads.microsoft.com

    0.0.0.0win10.ipv6.microsoft.com

    0.0.0.0watson.telemetry.microsoft.com

    0.0.0.0watson.microsoft.com0.

    0.0.0watson.live.com

    0.0.0.0vortex-win.data.microsoft.com

    0.0.0.0vortex.sandbox.data.microsoft.com

    0.0.0.0vortex.data.microsoft.com

    0.0.0.0vortex-cy2.metron.live.com.nsatc.net

    0.0.0.0vortex-bn2.metron.live.com.nsatc.net

    0.0.0.0telemetry.urs.microsoft.com

    0.0.0.0telemetry.microsoft.com

    0.0.0.0telemetry.appex.bing.net

    0.0.0.0telemetry.appex.bing.net

    0.0.0.0telecommand.telemetry.microsoft.com.nsatc.net

    0.0.0.0telecommand.telemetry.microsoft.com

    0.0.0.0statsfe2.ws.microsoft.com

    0.0.0.0statsfe2.update.microsoft.com.akadns.net

    0.0.0.0statsfe1.ws.microsoft.com

    0.0.0.0static.2mdn.net

    0.0.0.0ssw.live.com

    0.0.0.0sqm.telemetry.microsoft.com.nsatc.net

    0.0.0.0sqm.telemetry.microsoft.com

    0.0.0.0sqm.df.telemetry.microsoft.com

    0.0.0.0sls.update.microsoft.com.akadns.net

    0.0.0.0settings-win.data.microsoft.com

    0.0.0.0settings-sandbox.data.microsoft.com

    0.0.0.0services.wes.df.telemetry.microsoft.com

    0.0.0.0secure.flashtalking.com

    0.0.0.0secure.adnxs.com

    0.0.0.0schemas.microsoft.akadns.net

    0.0.0.0reports.wes.df.telemetry.microsoft.com

    0.0.0.0redir.metaservices.microsoft.com

    0.0.0.0rad.msn.com

    0.0.0.0rad.live.com

    0.0.0.0preview.msn.com

    0.0.0.0pre.footprintpredict.com

    0.0.0.0onesettings-db5.metron.live.nsatc.net

    0.0.0.0oca.telemetry.microsoft.com.nsatc.net

    0.0.0.0oca.telemetry.microsoft.com

    0.0.0.0msntest.serving-sys.com

    0.0.0.0msnbot-65-55-108-23.search.msn.com

    0.0.0.0msftncsi.com

    0.0.0.0msedge.net

    0.0.0.0m.adnxs.com

    0.0.0.0live.rads.msn.com

    0.0.0.0lb1.www.ms.akadns.net

    0.0.0.0ipv6.msftncsi.com.edgesuite.net

    0.0.0.0ipv6.msftncsi.com

    0.0.0.0i1.services.social.microsoft.com.nsatc.net

    0.0.0.0i1.services.social.microsoft.com

    0.0.0.0hostedocsp.globalsign.com

    0.0.0.0h2.msn.com

    0.0.0.0h1.msn.com

    0.0.0.0g.msn.com

    0.0.0.0flex.msn.com

    0.0.0.0feedback.windows.com

    0.0.0.0feedback.search.microsoft.com

    0.0.0.0feedback.microsoft-hohm.com

    0.0.0.0ec.atdmt.com

    0.0.0.0e8218.ce.akamaiedge.net

    0.0.0.0e7502.ce.akamaiedge.net

    0.0.0.0e7341.g.akamaiedge.net

    0.0.0.0e2835.dspb.akamaiedge.net

    0.0.0.0diagnostics.support.microsoft.com

    0.0.0.0df.telemetry.microsoft.com

    0.0.0.0db3aqu.atdmt.com

    0.0.0.0cs1.wpc.v0cdn.net

    0.0.0.0corp.sts.microsoft.com

    0.0.0.0corpext.msitadfs.glbdns2.microsoft.com

    0.0.0.0compatexchange.cloudapp.net

    0.0.0.0c.msn.com

    0.0.0.0choice.microsoft.com.nsatc.net

    0.0.0.0choice.microsoft.com

    0.0.0.0cds26.ams9.msecn.net

    0.0.0.0cdn.atdmt.com

    0.0.0.0c.atdmt.com

    0.0.0.0bs.serving-sys.com

    0.0.0.0b.rad.msn.com

    0.0.0.0bingads.microsoft.com

    0.0.0.0b.ads2.msads.net

    0.0.0.0b.ads1.msn.com

    0.0.0.0az512334.vo.msecnd.net

    0.0.0.0az361816.vo.msecnd.net

    0.0.0.0a.rad.msn.com

    0.0.0.0any.edge.bing.com

    0.0.0.0a-msedge.net

    0.0.0.0aka-cdn-ns.adtech.de

    0.0.0.0aidps.atdmt.com

    0.0.0.0ads.msn.com

    0.0.0.0ads1.msn.com

    0.0.0.0ads1.msads.net

    0.0.0.0adnxs.com

    0.0.0.0adnexus.net

    0.0.0.0ad.doubleclick.net

    0.0.0.0ac3.msn.com

    0.0.0.0a.ads2.msn.com

    0.0.0.0a.ads2.msads.net

    0.0.0.0a.ads1.msn.com

    0.0.0.0a978.i6g1.akamai.net

    0.0.0.0a-0009.a-msedge.net

    0.0.0.0a-0008.a-msedge.net

    0.0.0.0a-0007.a-msedge.net

    0.0.0.0a-0006.a-msedge.net

    0.0.0.0a-0005.a-msedge.net

    0.0.0.0a-0004.a-msedge.net

    0.0.0.0a-0003.a-msedge.net

    0.0.0.0a-0002.a-msedge.net

    0.0.0.0a-0001.a-msedge.net

    0.0.0.0ui.skype.com

    0.0.0.0sO.2mdn.net

    0.0.0.0 watson.telemetry.microsoft.com.nsatc.net

    0.0.0.00.0.0.0 watson.telemetry.microsoft.com

    0.0.0.0 watson.ppe.telemetry.microsoft.com

    0.0.0.0 watson.microsoft.com.nsatc.net

    0.0.0.0 watson.live.com

    0.0.0.0 vortex-win.data.microsoft.com

    0.0.0.0 vortex-win.data.metron.live.com.nsatc.net

    0.0.0.0 vortex-sandbox.data.microsoft.com

    0.0.0.0 vortex-sandbox.data.glbdns2.microsoft.com

    0.0.0.0 vortex-db5.metron.live.com.nsatc.net

    0.0.0.0 vortex.data.microsoft.com

    0.0.0.0 vortex-cy2.metron.live.com.nsatc.net

    0.0.0.0 vortex-bn2.metron.live.com.nsatc.net

    0.0.0.0 vortex.data.metron.live.com.nsatc.net

    0.0.0.0 vortex.data.glbdns2.microsoft.com

    0.0.0.0 t.urs.microsoft.com.nsatc.net

    0.0.0.0 telemetry.urs.microsoft.com

    0.0.0.0telemetry.appex.search.prod.ms.akadns.net

    0.0.0.0 telemetry.appex.bing.net

    0.0.0.0telecommand.telemetry.microsoft.com.nsatc.net

    0.0.0.0 telecommand.telemetry.microsoft.com

    0.0.0.0 survey.watson.microsoft.com

    0.0.0.0 watson.microsoft.com

    0.0.0.0 support.msn.microsoft.akadns.net

    0.0.0.0 statsfe2.ws.microsoft.com.nsatc.net

    0.0.0.0 statsfe2.ws.microsoft.com

    0.0.0.0 statsfe2.update.microsoft.com.akadns.net

    0.0.0.0 statsfe1.ws.microsoft.com.nsatc.net

    0.0.0.0 statsfe1.ws.microsoft.com

    0.0.0.0 s.gateway.messenger.live.com

    0.0.0.0 ssw.live.com.nsatc.net

    0.0.0.0 ssw.live.com

    0.0.0.0 sqm.telemetry.microsoft.com.nsatc.net

    0.0.0.0 sqm.telemetry.microsoft.com

    0.0.0.0 sqm.df.telemetry.microsoft.com

    0.0.0.0 spyneteurope.microsoft.akadns.net

    0.0.0.0 spynetalt.microsoft.com

    0.0.0.0 spynetalt.microsoft.akadns.net

    0.0.0.0 spynet2.microsoft.com

    0.0.0.0 spynet2.microsoft.akadns.net

    0.0.0.0 sls.update.microsoft.com.akadns.net

    0.0.0.0 siweb.microsoft.akadns.net

    0.0.0.0 schemas.microsoft.akadns.net

    0.0.0.0 settings-win.data.microsoft.com

    0.0.0.0 settings-sandbox.data.microsoft.com

    0.0.0.0 settings-sandbox.data.glbdns2.microsoft.com

    0.0.0.0 settings.data.microsoft.com

    0.0.0.0 settings.data.glbdns2.microsoft.com

    0.0.0.0 services.wes.df.telemetry.microsoft.com

    0.0.0.0 reports.wes.df.telemetry.microsoft.com

    0.0.0.0 wes.df.telemetry.microsoft.com

    0.0.0.0 redir.metaservices.microsoft.com.edgesuite.net

    0.0.0.0 redir.metaservices.microsoft.com.akadns.net

    0.0.0.0 redir.metaservices.microsoft.com

    0.0.0.0 redirection.prod.cms.msn.com.akadns.net

    0.0.0.0 redirection.prod.cms.msn.com

    0.0.0.0 s0.2mdn.net

    0.0.0.0 static.2mdn.net

    0.0.0.0 secure.flashtalking.com

    0.0.0.0 m.hotmail.com

    0.0.0.0 cds26.ams9.msecn.net

    0.0.0.0 a.rad.msn.com

    0.0.0.0 ac3.msn.com

    0.0.0.0 b.ads1.msn.com

    0.0.0.0 b.ads2.msads.net

    0.0.0.0 b.rad.msn.com

    0.0.0.0 rad.live.com

    0.0.0.0 rad.msn.com

    0.0.0.0 ads.msn.com

    0.0.0.0 preview.msn.com

    0.0.0.0 pre.footprintpredict.com

    0.0.0.0 onesettings-hk2.metron.live.com.nsatc.net

    0.0.0.0 oca.telemetry.microsoft.com.nsatc.net

    0.0.0.0 oca.telemetry.microsoft.com

    0.0.0.0 legacy-redirection-neurope-prod-hp.cloudapp.net

    0.0.0.0 lb1.www.ms.akadns.net

    0.0.0.0 i.s1.social.ms.akadns.net

    0.0.0.0 i1.services.social.microsoft.com.nsatc.net

    0.0.0.0 i1.services.social.microsoft.com

    0.0.0.0 feedback.windows.com

    0.0.0.0 feedback.search.microsoft.com

    0.0.0.0 feedback.microsoft-hohm.com

    0.0.0.0 microsoft-hohm.com

    0.0.0.0 fe3.delivery.dsp.mp.microsoft.com.nsatc.net

    0.0.0.0 fe2.update.microsoft.com.akadns.net

    0.0.0.0 e9946.g.akamaiedge.net

    0.0.0.0 df.telemetry.microsoft.com

    0.0.0.0 cs1.wpc.v0cdn.net

    0.0.0.0 corp.sts.microsoft.com

    0.0.0.0 corpext.msitadfs.glbdns2.microsoft.com

    0.0.0.0 compatexchange.cloudapp.net

    0.0.0.0 choice.microsoft.com.nsatc.net

    0.0.0.0 choice.microsoft.com

    0.0.0.0 choice.live.com

    0.0.0.0 http://www.msftncsi.com

    0.0.0.0 msftncsi.com

    0.0.0.0 cdn.atdmt.com

    0.0.0.0 db3aqu.atdmt.com

    0.0.0.0 c.atdmt.com

    0.0.0.0 ec.atdmt.com

    0.0.0.0 view.atdmt.com

    0.0.0.0 aidps.atdmt.com

    0.0.0.0 c.msn.com

    0.0.0.0 ca.telemetry.microsoft.com

    0.0.0.0 telemetry.microsoft.com

    0.0.0.0 msntest.serving-sys.com

    0.0.0.0 bs.serving-sys.com

    0.0.0.0 az512334.vo.msecnd.net

    0.0.0.0 az361816.vo.msecnd.net

    0.0.0.0 aka-cdn-ns.adtech.de

    0.0.0.0 ui.skype.com

    0.0.0.0 apps.skype.com

    0.0.0.0 ads2.msn.com.c.footprint.net

    0.0.0.0 live.rads.msn.com

    0.0.0.0 a.ads2.msads.net

    0.0.0.0 a.ads2.msn.com

    0.0.0.0 a.ads1.msn.com

    0.0.0.0 h1.msn.com

    0.0.0.0 h2.msn.com

    0.0.0.0 g.msn.com

    0.0.0.0 flex.msn.com

    0.0.0.0 ads2.msn.com

    0.0.0.0 ads1.msn.com

    0.0.0.0 ads1.msads.net

    0.0.0.0 m.adnxs.com

    0.0.0.0 secure.adnxs.com

    0.0.0.0 adnxs.com

    0.0.0.0 adnexus.net

    0.0.0.0 ad.doubleclick.net

    0.0.0.0 a1095.g2.akamai.net

    0.0.0.0 a-0009.a-msedge.net

    0.0.0.0 a-0008.a-msedge.net

    0.0.0.0 a-0007.a-msedge.net

    0.0.0.0 a-0006.a-msedge.net

    0.0.0.0 a-0005.a-msedge.net

    0.0.0.0 a-0004.a-msedge.net

    0.0.0.0 a-0003.a-msedge.net

    0.0.0.0 a-0003.amsedge.net

    0.0.0.0www.msftncsi.com

    0.0.0.0win10.ipv6.microsoft.com

    0.0.0.0wes.df.telemetry.microsoft.com

    0.0.0.0watson.telemetry.microsoft.com.nsatc.net

    0.0.0.0watson.telemetry.microsoft.com

    0.0.0.0watson.ppe.telemetry.microsoft.com

    0.0.0.0watson.microsoft.com

    0.0.0.0watson.live.com

    0.0.0.0vortex-win.data.microsoft.com

    0.0.0.0vortex-sandbox.data.microsoft.com

    0.0.0.0vortex-cy2.metron.live.com.nsatc.net

    0.0.0.0vortex-bn2.metron.live.com.nsatc.net

    0.0.0.0vortex.data.microsoft.com

    0.0.0.0view.atdmt.com

    0.0.0.0v10.vortex-win.data.microsoft.com

    0.0.0.0ui.skype.com

    0.0.0.0telemetry.urs.microsoft.com

    0.0.0.0telemetry.microsoft.com

    0.0.0.0telemetry.appex.bing.net

    0.0.0.0telemetry.appex.bing.net

    0.0.0.0telecommand.telemetry.microsoft.com.nsat-c.net

    0.0.0.0telecommand.telemetry.microsoft.com.nsatc.net

    0.0.0.0telecommand.telemetry.microsoft.com

    0.0.0.0survey.watson.microsoft.com

    0.0.0.0statsfe2.ws.microsoft.com

    0.0.0.0statsfe2.update.microsoft.com.akadns.net

    0.0.0.0statsfe1.ws.microsoft.com

    0.0.0.0static.2mdn.net

    0.0.0.0ssw.live.com

    0.0.0.0sqm.telemetry.microsoft.com.nsatc.net

    0.0.0.0sqm.telemetry.microsoft.com

    0.0.0.0sqm.df.telemetry.microsoft.com

    0.0.0.0spynetalt.microsoft.com

    0.0.0.0spynet2.microsoft.com

    0.0.0.0sO.2mdn.net

    0.0.0.0sls.update.microsoft.com.akadns.net

    0.0.0.0settings-win.data.microsoft.com

    0.0.0.0settings-sandbox.data.microsoft.com

    0.0.0.0settings.data.microsoft.com

    0.0.0.0services.wes.df.telemetry.microsoft.com

    0.0.0.0secure.flashtalking.com0.0.0.0secure.adnxs.com

    0.0.0.0schemas.microsoft.akadns.net

    0.0.0.0s0.2mdn.net

    0.0.0.0s.gateway.messenger.live.com

    0.0.0.0reports.wes.df.telemetry.microsoft.com

    0.0.0.0redir.metaservices.microsoft.com

    0.0.0.0rad.msn.com

    0.0.0.0rad.live.com

    0.0.0.0pricelist.skype.com

    0.0.0.0preview.msn.com

    0.0.0.0pre.footprintpredict.com

    0.0.0.0oca.telemetry.microsoft.com.nsatc.net

    0.0.0.0oca.telemetry.microsoft.com

    0.0.0.0msntest.serving-sys.com

    0.0.0.0msnbot-65-55-108-23.search.msn.com

    0.0.0.0msnbot-207-46-194-33.search.msn.com

    0.0.0.0msftncsi.com

    0.0.0.0msedge.net

    0.0.0.0m.hotmail.com

    0.0.0.0m.adnxs.com

    0.0.0.0live.rads.msn.com

    0.0.0.0lb1.www.ms.akadns.net

    0.0.0.0i1.services.social.microsoft.com.nsatc.net

    0.0.0.0i1.services.social.microsoft.com

    0.0.0.0h1.msn.com

    0.0.0.0g.msn.com

    0.0.0.0flex.msn.com

    0.0.0.0feedback.windows.com

    0.0.0.0feedback.search.microsoft.com

    0.0.0.0feedback.microsoft-hohm.com

    0.0.0.0fe3.delivery.dsp.mp.microsoft.com.nsatc.net

    0.0.0.0fe2.update.microsoft.com.akadns.net

    0.0.0.0ec.atdmt.com

    0.0.0.0diagnostics.support.microsoft.com

    0.0.0.0df.telemetry.microsoft.com

    0.0.0.0db3wns2011111.wns.windows.com

    0.0.0.0db3aqu.atdmt.com

    0.0.0.0cs1.wpc.v0cdn.net

    0.0.0.0corpext.msitadfs.glbdns2.microsoft.com

    0.0.0.0corp.sts.microsoft.com

    0.0.0.0compatexchange.cloudapp.net

    0.0.0.0choice.microsoft.com.nsatc.net

    0.0.0.0choice.microsoft.com

    0.0.0.0cds26.ams9.msecn.net

    0.0.0.0cdn.atdmt.com

    0.0.0.0cache.datamart.windows.com

    0.0.0.0ca.telemetry.microsoft.com

    0.0.0.0c.msn.com

    0.0.0.0c.atdmt.com

    0.0.0.0bs.serving-sys.com

    0.0.0.0b.rad.msn.com

    0.0.0.0b.ads2.msads.net

    0.0.0.0b.ads1.msn.com

    0.0.0.0az512334.vo.msecnd.net

    0.0.0.0az361816.vo.msecnd.net

    0.0.0.0apps.skype.com

    0.0.0.0a-msedge.net

    0.0.0.0aka-cdn-ns.adtech.de

    0.0.0.0aidps.atdmt.com

    0.0.0.0ads1.msn.com

    0.0.0.0ads1.msads.net

    0.0.0.0ads.msn.com

    0.0.0.0adnxs.com

    0.0.0.0adnexus.net

    0.0.0.0ad.doubleclick.net

    0.0.0.0ac3.msn.com

    0.0.0.0a-0009.a-msedge.net

    0.0.0.0a-0008.a-msedge.net

    0.0.0.0a-0007.a-msedge.net

    0.0.0.0a-0006.a-msedge.net

    0.0.0.0a-0005.a-msedge.net

    0.0.0.0a-0004.a-msedge.net

    0.0.0.0a-0003.a-msedge.net

    0.0.0.0a-0002.a-msedge.net

    0.0.0.0a-0001.a-msedge.net

    0.0.0.0a.rad.msn.com

    0.0.0.0a.ads2.msn.com

    0.0.0.0a.ads2.msads.net

    0.0.0.0a.ads1.msn.com

    This is what lars defends.

    Per M$ privacy statement

    We share your personal data with your consent

    This is what posters like lars defends in other articles when M$ are questioned about so much data gathering.

    windows being used in business, governments, medical institutions etc is terrifying with the amount of data they collect by default and data collection that can not be turned off with a toggle.

    1. Karol said on March 9, 2021 at 11:34 am
      Reply

      no sh1t Sherlock…

      1. you have choices to include those in your DNS filter of your router/pihole
      2. even better include it in your host file configuration and block them all
      3. most elegant is to deploy your own firewall rules, easily manageable (there is full Power Shell support) if anything goes wrong. It is also ‘on-eyes’ unlike host file.

      Windows has been privacy invasive for ages hence we have Sophia scripts, W10Privacy.de or privacy sexy, to mention those I prefer to use in my builds…

      1. Anon7 said on March 9, 2021 at 5:52 pm
        Reply

        @Karol

        > 1. you have choices to include those in your DNS filter of your router/pihole
        2. even better include it in your host file configuration and block them all
        3. most elegant is to deploy your own firewall rules, easily manageable (there is full Power Shell support) if anything goes wrong. It is also ‘on-eyes’ unlike host file.

        You know that most if not all of it can be blocked, i know it can be blocked with firewall/router rules.

        My point is how many average joes and average janes in administrative business roles or medical roles or governmental roles are implementing such a feature?

        My guess would be very little. That makes M$ literally running the world on their machines. That sounds horrifying IMO.

        Are you happy that such systems are holding your info like drivers license details etc?

        > Windows has been privacy invasive for ages hence we have Sophia scripts, W10Privacy.de or privacy sexy, to mention those I prefer to use in my builds…

        Yup, third party extensions are great to reclaim some bit of privacy back.

        But, how many people in administrative business roles or governmental roles even know or use such features?

        My guess? Very few and far between, M$ OS is literally running the worlds computer infrastructure. Which gives them unimaginable power and influence, which is way too much for a single corporation.

        That was the point i am making.

  3. Nico said on March 9, 2021 at 10:19 am
    Reply

    Why on earth this enormous wall of text?
    And it’s full of errors as well:
    there should be a space between 0.0.0.0 and the domain…
    So, `0.0.0.0a.ads1.msn.com`, should be `0.0.0.0 a.ads1.msn.com`

    1. Anonymous said on March 9, 2021 at 3:07 pm
      Reply
    2. Anon7 said on March 9, 2021 at 5:56 pm
      Reply

      @Niko

      Sorry for the big wall, its just making a point.

      However it is M$ enabling all that privacy invading stuff by default with sneaky consent forms that average people don’t care about, it is just wrong,

      Those average people are innocent and should be protected from such tracking by default.

  4. Anonymous said on March 9, 2021 at 3:24 pm
    Reply

    m$ hard codes IP’s in dll’s, hosts file won’t help you there.

  5. Tim Segulin said on March 9, 2021 at 4:42 pm
    Reply

    This nonsense was a major impetus for my moving to Linux.

  6. Marti Martz said on March 9, 2021 at 9:47 pm
    Reply

    Windows 10 (Oct 2020) installation with recent Windows Update (WUD) tried to update a clients machines video driver I was working on a few days ago.

    The card is an older one… MSI Radeon R7 360

    WUD tried to convert it to a R9 360. I had to install AMD’s WHQL driver to correctly get it functioning back to normal and detected as what it really was… an R7 360.

    So this is kind of terrifying to read that Microsoft may update drivers at their whim.

    1. EP said on March 10, 2021 at 5:39 pm
      Reply

      and you are not using MS’s wushowhide.diagcab tool to hide/block unwanted driver updates from MS, Marti?

      good thing I downloaded MS’s old wushowhide.diagcab tool before they recently took it down from their support site

  7. Robbie said on March 11, 2021 at 2:08 am
    Reply

    Wowie, comments section looks like Troll Central!

  8. noSign said on March 11, 2021 at 11:16 am
    Reply

    Disable Driver updates.reg

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\current\device\Update]
    “ExcludeWUDriversInQualityUpdate”=dword:00000001

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\default\Update]
    “ExcludeWUDriversInQualityUpdate”=dword:00000001

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\default\Update\ExcludeWUDriversInQualityUpdate]
    “value”=dword:00000001

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings]
    “ExcludeWUDriversInQualityUpdate”=dword:00000001

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
    “ExcludeWUDriversInQualityUpdate”=dword:00000001

Leave a Reply

Check the box to consent to your data being stored in line with the guidelines set out in our privacy policy

We love comments and welcome thoughtful and civilized discussion. Rudeness and personal attacks will not be tolerated. Please stay on-topic.
Please note that your comment may not appear immediately after you post it.