Thank you for your reply. I was just about to run the MRT. I checked the date. It is indeed the August 2011 tool, timestamp 2011-07-30 10:40:34 am, Digital Signature is 12:44:15 pm. I have also noticed something that may be the reason that the Windows Updates refuse to run--despite the fact that the Action Center reports nothing amiss/no action needs to be taken; AND the C:\HOTFIX folder contains files with dates no later than April---which means that although my list of installed updates in Control Panel shows 70 updates installed since 9/1, NONE of them have actually taken effect for some reason---most likely due to the certificate validation/timestamping error mentioned in a previous posting. Please pardon the runon sentences and circuitous thought processes, but what I have noticed is that .NET and Visual Studio are completely screwed up in several ways; chiefly among them are timestamping issues and "Compatability" and "Compatability Data". I had an error message in Event Viewer (I had to go scrounging for it; it was hard to find!) that "the 'flavor' or version of Microsoft Visual Studio did not match". When I looked closer, I discovered that I have Visual Studio 2005 and 2008, but data from Visual Studio 2010; with product versions 10.0.30319 and 10.0.30319.1. (Both numbers are product versions; not a product version and a file version) Each is the same for 32-bit and 64-bit. For all this mess, Permissions granted are 'Read' and 'Execute' to IIS_IUSRS (Anonymous Web users) Granting the Anonymous web user Read and Execute privileges to .Net and Visual Basic applications and data on a machinecan't possibly be a good idea! Correct me if I'm wrong...
(I have no web server enabled on this machine, no remote access applications; it's a standalone system with no home network; built specifically without a wireless card) There is a very long list of such privileges having been granted (not by me!) by the time I received the machine. I noticed something on the new 9/1 HD that wasn't on the OEM Dell HD from 8/16: SQL Server 2005 Compact Edition, which I have read in the bulletin boards as having conflicts with .NET,Visual Studio...I have seen so many conflicts ---including numerous I/O and Memory Resource Conflicts between key system devices that my teeth hurt from all the jaw-clenching! :-(
There are also cryptographic applications running that I did not configure; which could indicate to me that I may be 'locked out' of portions/partitions?) of my own hard drive? I have 409 GB free of 452 available GB, on a 500 GB HD--brand new; with basically no data on it yet. I know I'm not going to get every single kb of storage out of this 500GB HD, but how much space can an OS take up?? Certainly not close to 100 GB--there are no on-board backups, and only the Dell diagnostics, etc--which I wonder would even be effective. Kaspersky and TrendMicro Housecall report nothing unusual going on. It's only due to prior experience with oddly-dated timestamps/DigSigs that I even had reason to go snooping aroung. In the earlier case, I had a Vista machine with RunDll32, Consent.exe, et. al with 1969 dates, and MS Visual Basic with a 1904 date. FSUtil.exe had a date of AD 1601. There were other examples on that machine of JDLR--Just Doesn't Look Right---and that machine NEVER went online...Keeping it offline was the only way to prove to the mfr and to the retailer that these "hacks" (for want of a better word) were not the result of "Stupid Human Tricks". Kaspersky picked up 4 critical vulnerabilities on that machine; including a "suspicious' svchost.exe; with 16 month old virus definitions and signatures. I'm not a programmer, but I'm not so much of a neophyte that I can turn a blind eye to these anomalies. I'm a statistician by training, and all of these add up to much more than coincidence!
I'm going to try the Dell Diagnostics and the MRT-- in that order. It may be time to once again ask Dell to 'pretty-please-stop-fannying-about' and provide some of their stellar customer service... I really do appreciate your input. You've given me something to go on---and some hope!