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

Re: Today's "Windows 10 concern"

From	...w¡ñ§±¤ñ <winstonmvp@gmail.com>
Newsgroups	alt.comp.os.windows-10
Subject	Re: Today's "Windows 10 concern"
Date	2025-03-07 01:02 -0700
Organization	windowsunplugged.com
Message-ID	<vqe96j$3ehga$1@dont-email.me> (permalink)
References	<vq9imi$2e7gt$1@dont-email.me> <gmcksj132crppdl2jaf8bv1slma4vpn1s8@4ax.com>

Show all headers | View raw

micky wrote on 3/6/2025 4:45 PM:
> 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
  - that folder was a deploymenent location for a monthly update.
  - the functionality of DeviceCensus.exe in Windows does not use that 
location.
  - the folder only indicates that the folder was created sometime in the 
past for updating Windows.
- Windows 10 22H2 or earlier(19041 is Win10 20H2 base, though 19041 files 
are still in use on later Win10 versions).
   e.g Win10 22H2's DeviceCensus.exe is still 19041 version, and its 
DeviceCensus.exe should be 19041.5438 at the minimum 22H2 updated through 
Feb 2025(019041.5487)
  => and its file date should be the date that the last LCU(monthly 
update) was installed(i.e. if you installed February's LCU today on March 
7, then the DeviceCensus.exe file Creatrion and Modified Date should be 
March 7 2025. The exe file's Digital Signature should have a date in Jan. 
or Feb 2025(when Win10 has been updated with the latest(Feb) LCU.> I 
wonder what the difference in locations means.
> I haven't checked if it runs or not.
In your case, it does not mean much for running an exe. That location is 
unused for the installed Windows version.
No reason to check.
  - If you wish to run DeviceCensus.exe find the exe in 
C:\Windows\System32 and double click to run it...but doing so won't 
provide much information.


-- 
...w¡ñ§±¤ñ

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