Can Microsoft Explain This?

Hi,

I am a computer enthusiast and have been building my own pc's for years.
The problem i have is that Windows Xp Home Edition sets up my system as a
win2000 machine and not as advertised on my boxed case. I have two boxed
retail versions of winxp home edition and are 100% genuine. I do not have any
illegal software fullstop.

Now onto the problem.

I set this machine up on the 26th of April. The file tsoc.text (c:windows)
clearly shows the install setting the machine to a win2000 box.

*******Initializing Message Log:tsoc.dll 04/26/06 09:12:04
*******Version:Major=5, Minor=1, Build=2600, PlatForm=2, CSDVer=Service Pack
2, Free

hydraoc.cpp(188)Entering OC_PREINITIALIZE
hydraoc.cpp(189)Component=terminalserver, SubComponent=???????
hydraoc.cpp(297)OC_PREINITIALIZE Done. Returning 1

hydraoc.cpp(188)Entering OC_INIT_COMPONENT
hydraoc.cpp(189)Component=terminalserver, SubComponent=(null)
state.cpp(1006)Setup Parameters ****************************
state.cpp(1007)We are running on Wks
state.cpp(1008)Is this adv server No
state.cpp(1009)Is this Personal (Home Edition) Yes
state.cpp(1010)Is this SBS server No
state.cpp(1011)IsStandAloneSetup = No
state.cpp(1012)IsFreshInstall = Yes
state.cpp(1013)IsTSFreshInstall = Yes
state.cpp(1014)IsUnattendSetup = No
state.cpp(1015)IsUpgradeFromTS40 = No
state.cpp(1016)IsUpgradeFromNT50 = No
state.cpp(1017)IsUpgradeFromNT51 = No
state.cpp(1018)IsUnattended = No
state.cpp(1020)Original State ******************************
state.cpp(1021)WasTSInstalled = No
state.cpp(1022)WasTSEnabled = No
state.cpp(1023)OriginalPermMode = WIN2K
state.cpp(1037)Original TS Mode = TS Disabled
state.cpp(1050)Current State ******************************
state.cpp(1065)New TS Mode = Personal TS
state.cpp(1075)New Permissions Mode = PERM_WIN2K
state.cpp(1084)New Connections Allowed = False
hydraoc.cpp(297)OC_INIT_COMPONENT Done. Returning 0

The Windows update site clarify's this when i have a look at the related
knowledge base fixes. A Typical one reads like this:

[KB873339.log]
1.156:
================================================== ==============================
1.156: 2006/04/26 11:46:11.703 (local)
1.156:
C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\70bee86dd2b52f0c3f60c71113182f25\update\update. exe (version 5.5.33.0)
1.156: Service Pack started with following command line: /si
/ParentInfo:de92fb9c37de8f44b48636359f905d3c
1.734: DoInstallation: CleanPFR failed: 0x2
1.766: SetProductTypes: InfProductBuildType=BuildType.IC
1.766: SetAltOsLoaderPath: No section uses DirId 65701; done.
1.766: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB873339$
1.766: LoadFileQueues: SetupGetSourceFileLocation for halaacpi.dll failed:
0xe0000102
1.781: ref tag c:\windows\system32\sp4.cab does not exist
1.781: ref tag c:\windows\system32\sp3.cab does not exist
1.781: ref tag c:\windows\system32\sp2.cab does not exist
1.781: ref tag c:\windows\system32\sp1.cab does not exist
1.781: ref tag c:\windows\system32\driver.cab does not exist
1.781: ref tag c:\windows\system32\fp40ext.cab does not exist
1.781: ref tag c:\windows\system32\fp40ext1.cab does not exist
1.781: ref tag c:\windows\system32\wms4.cab does not exist
1.781: ref tag c:\windows\system32\wms41.cab does not exist
1.781: ref tag c:\windows\system32\ims.cab does not exist
1.781: ref tag c:\windows\system32\ims1.cab does not exist
1.781: ref tag c:\windows\system32\ins.cab does not exist
1.781: ref tag c:\windows\system32\ins1.cab does not exist
1.781: Starting AnalyzeComponents
1.781: AnalyzePhaseZero used 0 ticks
1.781: No c:\windows\INF\updtblk.inf file.
1.781: OEM file scan used 0 ticks
1.797: AnalyzePhaseOne: used 16 ticks
1.797: AnalyzeComponents: Hotpatch analysis disabled; skipping.
1.797: AnalyzeComponents: Hotpatching is disabled.
1.797: FindFirstFile c:\windows\$hf_mig$\*.*
1.812: AnalyzeForBranching used 0 ticks.
1.812: AnalyzePhaseTwo used 0 ticks
1.812: AnalyzePhaseThree used 0 ticks
1.828: AnalyzePhaseFive used 16 ticks
1.828: AnalyzePhaseSix used 0 ticks
1.828: AnalyzeComponents used 47 ticks
1.828: Downloading 2 files
1.828: bPatchMode = TRUE
1.828: Inventory complete: ReturnStatus=0, 62 ticks
1.828: Num Ticks for invent : 62
1.844: [dumpDownloadTask] Update.exe posting request file to download a
total of 36932 bytes (36932 bytes in patches and 0 bytes in fallbacks)
1.844: [dumpDownloadTask] Returning 0xf200
1.844: dumpDownloadTask returned 0xf200 (more files to download)
1.859: KB873339 installation did not complete.
1.859: Update.exe extended error code = 0xf200
2.453: FindFirstFile c:\windows\$hf_mig$\*.*
2.468: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.484: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.484: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.500: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.500: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.500: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.500: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.500: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.500: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.500: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.500: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.500: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.500: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.500: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.500: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.500: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.500: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.515: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.515: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.515: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.515: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.515: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.515: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.515: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.515: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.531: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.531: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.531: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.531: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.531: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.531: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.531: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.547: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.547: KB873339 Setup encountered an error: The update.ver file is not
correct.
2.562: AnalyzeForBranching used 0 ticks.
2.578: AnalyzePhaseTwo used 16 ticks
2.578: AnalyzePhaseThree used 0 ticks
2.593: AnalyzePhaseFive used 15 ticks
2.593: AnalyzePhaseSix used 0 ticks
2.593: AnalyzeComponents used 140 ticks
2.593: Downloading 2 files
2.593: bPatchMode = TRUE
2.593: Inventory complete: ReturnStatus=0, 187 ticks
2.609: Num Ticks for invent : 203
2.625: [dumpDownloadTask] Update.exe posting request file to download a
total of 36932 bytes (36932 bytes in patches and 0 bytes in fallbacks)
2.625: [dumpDownloadTask] Returning 0xf200
2.625: dumpDownloadTask returned 0xf200 (more files to download)
2.734: KB873339 installation did not complete.
2.734: Update.exe extended error code = 0xf200
0.578:

This clearly shows that the patches haven't taken and every fix is the same.
Some show that the fix is testing a volitile flag in the registery and fails.
Here is an example:

[KB910437.log]
0.546:
================================================== ==============================
0.546: 2006/04/26 11:53:59.484 (local)
0.546:
C:\WINDOWS\SoftwareDistribution\Download\f14f8865d d08e4d95c38a2ae4cb1096f\update\update.exe (version 6.2.29.0)
0.546: Failed To Enable SE_SHUTDOWN_PRIVILEGE
0.546: Hotfix started with following command line: -q -z -er
/ParentInfo:ba136daabc1e4348883519f3de382a35
0.687: In Function TestVolatileFlag, line 11873, RegOpenKeyEx failed with
error 0x2
0.687: In Function TestVolatileFlag, line 11905, RegQueryValueEx failed with
error 0x2
0.687: DoInstallation: CleanPFR failed: 0x2
0.687: SetProductTypes: InfProductBuildType=BuildType.IC
0.687: SetAltOsLoaderPath: No section uses DirId 65701; done.
0.703: DoInstallation: FetchSourceURL for
c:\windows\softwaredistribution\download\f14f8865d d08e4d95c38a2ae4cb1096f\update\update_SP2GDR.inf failed
0.703: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB910437$
0.703: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
0xe0000102
0.703: BuildCabinetManifest: update.url absent
0.703: Starting AnalyzeComponents
0.703: AnalyzePhaseZero used 0 ticks
0.703: No c:\windows\INF\updtblk.inf file.
0.703: OEM file scan used 0 ticks
0.781: AnalyzePhaseOne: used 78 ticks
0.781: AnalyzeComponents: Hotpatch analysis disabled; skipping.
0.781: AnalyzeComponents: Hotpatching is disabled.
0.781: FindFirstFile c:\windows\$hf_mig$\*.*
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.781: KB910437 Setup encountered an error: The update.ver file is not
correct.
0.796: AnalyzeForBranching used 15 ticks.
0.796: AnalyzePhaseTwo used 0 ticks
0.796: AnalyzePhaseThree used 0 ticks
0.796: AnalyzePhaseFive used 0 ticks
0.796: AnalyzePhaseSix used 0 ticks
0.796: AnalyzeComponents used 93 ticks
0.796: Downloading 0 files
0.796: bPatchMode = FALSE
0.796: Inventory complete: ReturnStatus=0, 93 ticks
0.796: Num Ticks for invent : 93
0.812: VerifyTargetFileSize: Unable to verify size as Source = NULL for file
c:\windows\inf\HFX1AF.tmp
0.812: Copied file: c:\windows\inf\branches.inf
0.812: Allocation size of drive C: is 4096 bytes, free space = 195916902400
bytes
0.812: AnalyzeDiskUsage: Skipping EstimateDiskUsageForUninstall.
0.812: Drive C: free 186840MB req: 12MB w/uninstall: NOT CALCULATED.
0.812: CabinetBuild complete
0.812: Num Ticks for Cabinet build : 16
0.812: DynamicStrings section not defined or empty.
0.812: FileInUse:: Detection disabled.
1.812: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
0xe0000102
1.828: Num Ticks for Backup : 1016
1.937: Num Ticks for creating uninst inf : 109
1.937: Registering Uninstall Program for -> KB910437, KB910437 , 0x0
1.937: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
0xe0000102
1.937: System Restore Point set.
2.000: Copied file: C:\WINDOWS\system32\spmsg.dll
2.000: PFE2: Not avoiding Per File Exceptions.
2.015: GetCatVersion: Failed to retrieve version information from
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\KB910437.cat with error 0x57

Another KB apparent fix shows that whatever has my machine definately has
control of my hardware. The KB fix looks like this

[KB911565.log]
0.172:
================================================== ==============================
0.172: 2006/04/26 11:54:22.187 (local)
0.172:
C:\WINDOWS\SoftwareDistribution\Download\48558b66e f3ff75ac65bf84682e6f852\update\update.exe (version 6.2.29.0)
0.203: DoInstallation: GetProcAddress(InitializeCustomizationDLL) Returned:
0x7f
0.203: Failed To Enable SE_SHUTDOWN_PRIVILEGE
0.203: Hotfix started with following command line: -q -z -er
/ParentInfo:4cf5413fc39e9e41bdc0fb59d389e283
0.218: C:\WINDOWS\system32\wmp.dll is Present
0.218: FileVersion of C:\WINDOWS\system32\wmp.dll is Greater or Equal To
10.0.0.3646
0.218: Condition succeeded for section Test.FileVer.Section in Line 1 of
PreRequisite
0.375: ---- Old Information In The Registry ------
0.375: Source:C:\WINDOWS\system32\SET1B0.tmp (5.1.2600.2780)
0.375: Destination:C:\WINDOWS\system32\esent.dll (5.1.2600.2180)
0.375: ---- New Information In The Registry ------
0.375: Source:C:\WINDOWS\system32\SET1B0.tmp (5.1.2600.2780)
0.375: Destination:C:\WINDOWS\system32\esent.dll (5.1.2600.2180)
0.375: SetProductTypes: InfProductBuildType=BuildType.IC
0.375: SetAltOsLoaderPath: No section uses DirId 65701; done.
0.375: DoInstallation: FetchSourceURL for
c:\windows\softwaredistribution\download\48558b66e f3ff75ac65bf84682e6f852\update\update.inf failed
0.375: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB911565$
0.375: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
0xe0000102
0.375: BuildCabinetManifest: update.url absent
0.375: Starting AnalyzeComponents
0.375: AnalyzePhaseZero used 0 ticks
0.375: No c:\windows\INF\updtblk.inf file.
0.375: SetupFindFirstLine in LoadExclusionList Failed with error: 0xe0000102
0.375: SetupFindFirstLine in LoadExclusionList Failed with error: 0xe0000102
2.937:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem6.CAT
trusts inf c:\windows\inf\oem6.inf of device
NVAX\NFORCE_VAD\4&212292CD&0&0000
3.453:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem2.CAT
trusts inf c:\windows\inf\oem2.inf of device
PCI\VEN_10DE&DEV_0052&SUBSYS_815A1043&REV_A2\3&241 1E6FE&0&09
5.906:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT
trusts inf c:\windows\inf\oem1.inf of device
PCI\VEN_10DE&DEV_005E&SUBSYS_815A1043&REV_A3\3&241 1E6FE&0&00
7.422: Failed to query DriverPath of ROOT\LEGACY_AFD\0000 0x2
7.422: Failed to query DriverPath of ROOT\LEGACY_AMON\0000 0x2
7.422: Failed to query DriverPath of ROOT\LEGACY_BEEP\0000 0x2
7.422: Failed to query DriverPath of ROOT\LEGACY_DMBOOT\0000 0x2
7.422: Failed to query DriverPath of ROOT\LEGACY_DMLOAD\0000 0x2
7.422: Failed to query DriverPath of ROOT\LEGACY_FIPS\0000 0x2
7.422: Failed to query DriverPath of ROOT\LEGACY_GPC\0000 0x2
7.422: Failed to query DriverPath of ROOT\LEGACY_HTTP\0000 0x2
7.422: Failed to query DriverPath of ROOT\LEGACY_IPNAT\0000 0x2
7.422: Failed to query DriverPath of ROOT\LEGACY_IPSEC\0000 0x2
7.422: Failed to query DriverPath of ROOT\LEGACY_KSECDD\0000 0x2
7.422: Failed to query DriverPath of ROOT\LEGACY_MNMDD\0000 0x2
7.422: Failed to query DriverPath of ROOT\LEGACY_MOUNTMGR\0000 0x2
7.422: Failed to query DriverPath of ROOT\LEGACY_NDIS\0000 0x2
7.422: Failed to query DriverPath of ROOT\LEGACY_NDISTAPI\0000 0x2
7.422: Failed to query DriverPath of ROOT\LEGACY_NDISUIO\0000 0x2
7.422: Failed to query DriverPath of ROOT\LEGACY_NDPROXY\0000 0x2
7.422: Failed to query DriverPath of ROOT\LEGACY_NETBT\0000 0x2
7.422: Failed to query DriverPath of ROOT\LEGACY_NULL\0000 0x2
7.422: Failed to query DriverPath of ROOT\LEGACY_PARTMGR\0000 0x2
7.422: Failed to query DriverPath of ROOT\LEGACY_PARVDM\0000 0x2
7.422: Failed to query DriverPath of ROOT\LEGACY_RASACD\0000 0x2
7.422: Failed to query DriverPath of ROOT\LEGACY_RDPCDD\0000 0x2
7.422: Failed to query DriverPath of ROOT\LEGACY_TCPIP\0000 0x2
7.422: Failed to query DriverPath of ROOT\LEGACY_VGASAVE\0000 0x2
7.422: Failed to query DriverPath of ROOT\LEGACY_VOLSNAP\0000 0x2
7.422: Failed to query DriverPath of ROOT\LEGACY_WANARP\0000 0x2
7.437: Failed to query DriverPath of ROOT\LEGACY_WS2IFSL\0000 0x2
10.140: OEM file scan used 9765 ticks
10.468: AnalyzePhaseOne: used 10093 ticks
10.468: AnalyzeComponents: Hotpatch analysis disabled; skipping.
10.468: AnalyzeComponents: Hotpatching is disabled.
10.468: AnalyzePhaseTwo used 0 ticks
10.468: AnalyzePhaseThree used 0 ticks
10.468: AnalyzePhaseFive used 0 ticks
10.468: AnalyzePhaseSix used 0 ticks
10.484: AnalyzeComponents used 10109 ticks
10.484: Downloading 0 files
10.484: bPatchMode = FALSE
10.484: Inventory complete: ReturnStatus=0, 10109 ticks
10.484: Num Ticks for invent : 10109
10.484: Allocation size of drive C: is 4096 bytes, free space = 195905822720
bytes
10.484: AnalyzeDiskUsage: Skipping EstimateDiskUsageForUninstall.
10.484: Drive C: free 186830MB req: 5MB w/uninstall: NOT CALCULATED.
10.484: CabinetBuild complete
10.484: Num Ticks for Cabinet build : 0
10.484: DynamicStrings section not defined or empty.
10.484: FileInUse:: Added to Filelist: c:\windows\kb911565.cat
10.484: FileInUse:: Added to Filelist: c:\windows\system32\wmp.dll
10.484: FileInUse:: Added to Filelist: c:\windows\system32\dllcache\wmp.dll
10.500: FileInUse:: PrintTasksUsingModule: No tasks found using
c:\windows\kb911565.cat
10.515: FileInUse:: PrintTasksUsingModule: No tasks found using
c:\windows\system32\wmp.dll
10.531: FileInUse:: PrintTasksUsingModule: No tasks found using
c:\windows\system32\dllcache\wmp.dll
11.531: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
0xe0000102
11.547: Num Ticks for Backup : 1063
11.625: Num Ticks for creating uninst inf : 78
11.656: Registering Uninstall Program for -> KB911565, KB911565 , 0x0
11.750: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
0xe0000102
11.859: System Restore Point set.
11.890: Copied file: C:\WINDOWS\system32\spmsg.dll
11.890: PFE2: Not avoiding Per File Exceptions.
11.890: GetCatVersion: Failed to retrieve version information from
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\KB911565.cat with error 0x57
11.953: Copied file: C:\WINDOWS\system32\wmp.dll
12.234: Copied file: C:\WINDOWS\system32\DllCache\wmp.dll
12.250: DoInstallation: Installing assemblies with source root path:
c:\windows\softwaredistribution\download\48558b66e f3ff75ac65bf84682e6f852\
12.250: Num Ticks for Copying files : 625
12.250: Num Ticks for Reg update and deleting 0 size files : 0
12.250: Starting process: C:\WINDOWS\system32\spupdsvc.exe /install
"Enables Installer to complete its scheduled post-reboot tasks"
12.359: Return Code = 0
12.375: ---- Old Information In The Registry ------
12.375: Source:C:\WINDOWS\system32\SET1B0.tmp (5.1.2600.2780)
12.375: Destination:C:\WINDOWS\system32\esent.dll (5.1.2600.2180)
12.375: ---- New Information In The Registry ------
12.375: Source:C:\WINDOWS\system32\SET1B0.tmp (5.1.2600.2780)
12.375: Destination:C:\WINDOWS\system32\esent.dll (5.1.2600.2180)
12.922: UpdateSpUpdSvcInf: Source [ProcessesToRunAfterReboot] section is
empty; nothing to do.
12.922: Starting process: C:\WINDOWS\inf\unregmp2.exe /UpdateWMP
13.093: Return Code = 0
13.109: RebootNecessary = 0,WizardInput = 1 , DontReboot = 1, ForceRestart = 0

I have had this problem for years now and have had to come online to try and
get this resolved. I have had no luck so far and to get Microsoft to admit
that they have lost control of their own operating systems is very hard.
Hopefully this will help.

The one that done it for me was under certain conditions i get a popup
saying "Should not see me". This is without fake security certs, unkown user
in the registery and a oblong symbol in my font folder that i have witnessed
remote controlling of the system.

I have been hacked big time from brand new pc equipment and an install of
WinXp.

CAN YOU EXPLAIN THIS MICROSOFT

Regards

sigma-

sigma-7 <sigma-> wrote:

> The problem i have is that Windows Xp Home Edition sets up my system
> as a win2000 machine and not as advertised on my boxed case.

Could you please explain what you mean by "sets up my system as a win2000
machine"

Your quoted logs are clear that you have Windows XP installed.

--
Robin Walker [MVP Networking]