cmd.exe file size - one black sheep?

[toffee_paul]

Hi,

 

I've just ran a custom report using PDQ Deploy to look at cmd.exe file sizes to make sure nobody is exploiting the well-known 'Ease-of-Access/utilman.exe/cmd.exe' hack and noticed that one computer has a different file size than the others.

 

All machines are running W7 Pro and are all fully updated so I can't get my head around why the cmd.exe on this one PC is a difference file size. It's even more strange as the 'File Created' field says it was created 1 day earlier than the files on all the other hundred-odd computers.

 

Any ideas?

 

(PDQ Deploy report screenshot below)

 

 

Thanks

[toffee_paul]

You know when something's bugging you then you have that lightbulb moment? Well figured it out last night whilst chopping onions...the CMD.exe on the black sheep machine is running 32bit Windows, the rest are 64bit. So that explains the file size difference. Doh!