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


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

Re: Today's "Windows 10 concern"

From micky <NONONOmisc07@fmguy.com>
Newsgroups alt.comp.os.windows-10
Subject Re: Today's "Windows 10 concern"
Message-ID <gmcksj132crppdl2jaf8bv1slma4vpn1s8@4ax.com> (permalink)
References <vq9imi$2e7gt$1@dont-email.me>
Organization Tweaknews
Date 2025-03-06 18:45 -0500

Show all headers | View raw


In alt.comp.os.windows-10, on Wed, 5 Mar 2025 05:13:51 -0800, "John C."
<r9jmg0@yahoo.com> wrote:

>So what is this "DeviceCensus.exe" executable (file path is
>C:\Windows\System32\DeviceCensus.exe, at least on my system)? The

Interestingly, I have the file too, 24KB, from 11/17/2024, but it's
address is:
C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.5371.1.9\amd64_microsoft-windows-devicecensus_31bf3856ad364e35_10.0.19041.5198_none_2445ede1afad7996\f

I wonder what the difference in locations means. 

I haven't checked if it runs or not.  I'm not sure what else besides
starting the router would cause it to perk up. 

>The internet says:
>
>"DeviceCensus.exe is a legitimate system file in Windows 10, signed by
>Microsoft. It is part of the Telemetry Framework and is located in the
>System32 folder. Its primary function is to collect data on your
>device's hardware usage, _including webcam usage_, and report it back to
>Microsoft. This helps Microsoft optimize Windows for future updates and
>fix any bugs.
>  If you notice that DeviceCensus.exe is using a lot of CPU or accessing
>your webcam, it is generally safe to keep it running. However, if you
>want to disable it temporarily, you can do so through the Task Scheduler.
>  If you have any concerns about privacy or security, it's always a good
>idea to run a thorough antivirus scan to ensure that your system is not
>infected with malware."

Back to alt.comp.os.windows-10 | Previous | NextPrevious 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