Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.comp.os.windows-10 > #182795

Re: Today's "Windows 10 concern"

Show all headers | View raw

Paul <nospam@needed.invalid> wrote:
[...]

> https://www.thewindowsclub.com/device-census-in-windows-10
> 
> These descriptions are a bit on the funny side.
> 
> It could be accessing the webcam, to collect PNP info, but
> that story is weak sauce. Unless the device has firmware
> it loads each time, and there are likely better ways to determine
> what firmware is being used, without probing the device.
> 
> The device has already been probed as part of hardware enumeration.
> And that effort should be all that is needed. If Microsoft
> wanted to use their command line version of Device Manager to
> dump the hardware details, they could do that, and then the
> webcam would never be blocked.

  AFAICT, this isn't really something to get one's knickers in a twist
about.

  During installation - at least on Windows 11 - there's a question
about this [1] and in Settings you can limit - but not eliminate - the
amount of 'Diagnostic data', you can 'View diagnostic data' and you can
'Delete diagnostic data'.

  For details: Settings -> Privacy & security -> Diagnostics & feedback

  If one decides to try to prevent Diagnostic data to be sent -
preferably based on the actual content -, then it's probably best to try
to block it in the firewall, instead of assuming/hoping that the Task
Scheduler task won't be re-enabled.

  FWIW, my 'Diagnostic data' setting is set to 'Sending required data'
and my computer hasn't been taken over by Microsoft (yet!? :-)).

[...]

[1] "Send diagnostic data to Microsoft" -> Required only -> [Accept]

Back to alt.comp.os.windows-10 | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Today's "Windows 10 concern" "John C." <r9jmg0@yahoo.com> - 2025-03-05 05:13 -0800
  Re: Today's "Windows 10 concern" Mr Xi Ji Ping <ping@china.cn> - 2025-03-05 18:00 +0000
  Re: Today's "Windows 10 concern" Paul <nospam@needed.invalid> - 2025-03-05 15:18 -0500
    Re: Today's "Windows 10 concern" Frank Slootweg <this@ddress.is.invalid> - 2025-03-06 10:33 +0000
    Re: Today's "Windows 10 concern" "John C." <r9jmg0@yahoo.com> - 2025-03-06 17:40 -0800
      Re: Today's "Windows 10 concern" Newyana2 <newyana@invalid.nospam> - 2025-03-07 08:31 -0500
        Re: Today's "Windows 10 concern" Paul <nospam@needed.invalid> - 2025-03-07 19:04 -0500
        Re: Today's "Windows 10 concern" The Car <arriving@dawn.com> - 2025-03-08 10:39 -0800
          Re: Today's "Windows 10 concern" Paul <nospam@needed.invalid> - 2025-03-08 14:36 -0500
  Re: Today's "Windows 10 concern" micky <NONONOmisc07@fmguy.com> - 2025-03-06 18:45 -0500
    Re: Today's "Windows 10 concern" Paul <nospam@needed.invalid> - 2025-03-06 20:15 -0500
    Re: Today's "Windows 10 concern" ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-03-07 01:02 -0700
      Re: Today's "Windows 10 concern" micky <NONONOmisc07@fmguy.com> - 2025-03-08 00:11 -0500

csiph-web