03-17-2012 05:00 PM
Solved! Go to Solution.
03-17-2012 05:53 PM
03-18-2012 01:29 AM - edited 03-18-2012 01:32 AM
Looking at the disassembled code. the wfpdot.exe seems to have been written by this guy: http://cz.linkedin.com/pub/ji%C5%99%C3%AD-margarit
Question is, what is this code doing on a Lenovo laptop? It seems to be related to "AuthenTec"...but still, W(hy)TF does it (the exe) need its own \root?
03-18-2012 10:27 AM
03-18-2012 11:20 AM - edited 03-18-2012 06:48 PM
AuthenTec bought UPEK some time ago.
03-18-2012 08:47 PM
Still doesn't explain why there's an unknown purpose .exe lying around at the root's root directory, one that seems like it was compiled by the individual instead of being built with the rest of the FPR software.
Who at Lenovo does system image control?
03-18-2012 09:38 PM
Chatbox wrote:Still doesn't explain why there's an unknown purpose .exe lying around at the root's root directory, one that seems like it was compiled by the individual instead of being built with the rest of the FPR software.
Who at Lenovo does system image control?
Agreed. This was not in the images for the first machines that came off the line. It has no business being there now. Hopefully for Lenovo's sake it isn't a keystroke logger or something.
03-19-2012 05:38 AM - edited 03-19-2012 05:38 AM
The date on the file on my system is 6/30/2010. WPF is Windows Programming Foundation which is .NET 3.0. My supposition is that this is leftover from the initial Windows 7 install of the FPR when instantiating the factory image. The date on the C;/Root folder is 6/1/11 which was when my system was built. I could find no running processes that use this code.
03-19-2012 05:45 AM - edited 03-19-2012 05:46 AM
The folder creation date and the exe's creation date are the same, "Monday, 5 March 2012, 1:30:37 AM".
This date is prior to me recieving the system, while the system was being built (it was shipped on the 6th).
So, I can say with a high certainty that this (file and folder) was created as part of the image's post-cloned process.
Lenovo should have tighter control / governance on what files are on the filing system that gets ship out to customers.
03-19-2012 05:51 AM
Yes, it's part of the original imaging process at the factory. That's why you are seeing the specific dates. Nof sure why the file date and the folder date are different. There are several other folders left on the C;\ such as \MFG for example.