The live system (Win7x32) is on C: but I get those errors about files on another partition (D:) where a 64bit Windows 7 is installed (multiboot in the same BCD located on the first, active – boot partition).
Here is the error:
Activation context generation failed for
“D:WindowsSystem32charmap.exe”. Assembly dependent
Microsoft.Windows.Common-Controls,language=”*”,processorArchitecture=
“amd64″,
publicKeyToken=”6595b64144ccf1df”,type=”win32″,version=”6.0.0.0″ could
not be found. Please use sxstrace.exe for detailed diagnosis.
I’ve got the same error about several other executable, all from D:Windows which is the 2nd installation and is Win7 64bit:
ComputerDefaults.exe
consent.exe
cofire.exe
AdapterTroubleshooter.exe
OptionalFeatures.exe
newdev.exe
NetProj.exe
pcaui.exe
perfmon.exe
ndadmin.exe
MultiDigiMon.exe
ntprint.exe
Netplwiz.exe
regedit.exe
These errors are cycling around in the eventlog several times. But sometimes only these 3 in that order:
consent.exe
charmap.exe
ComputerDefaults.exe
cofire.exe
As these are all 64bit exes, the error would be normal on a 32bit system, but why are they concerned here at all? (I didn’t try to launch them, of course.) What could want to access them from a 32bit system on another partition, that causes they appearing in the eventlog as error?
There is no occurrence in the registry of a “systemroot” such as “d:windows…” and in the BCD everything looks correct as well. So I can’t imagine why the 32bit OS claims about system files on the 64bit OS. Especially about an exe like charmap for example. Looks weird.
Here it has to be said that – when my previous laptop’s bios died (it was a Celeron based Acer variant) – I’ve put its hard disk into a (Pentium dual core based) Toshiba satellite (c650) and could happily keep my installations as all the changed hardware got installed (sure, after a first blue screen, that then later didn’t came back).
Then I thoroughly uninstalled/removed all inexistent devices and drivers left over from the previous machine (using Uwe Sieber’s tool: there is a topic here at Superuser about this). Everything worked, everything looked fine for a while… until a time that weird errors occurred and I could not find out why:
Some, not all, programs refused to launch, such as (ungoogled)chromium portable v.100+, but some older browsers for example did start. No network connections as well, with a socket error 11003 when using “netsh”. Microsoft says (here): “WSANO_RECOVERY : This is a nonrecoverable error. This indicates that some sort of nonrecoverable error occurred during a database lookup. This may be because the database files (for example, BSD-compatible HOSTS, SERVICES, or PROTOCOLS files) could not be found, or a DNS request was returned by the server with a severe error.”
Then, if doing a reboot, the login session lasts 5-10minutes with some services unable to start („start pending”) such as EventLog and DHCP client…
There is also a topic about this here at Superuser that points to Winsock/TCPIP corruption and repair, which is interesting, or here: but only partly related to my issue.
I first tried some repair via the “Windows Repair” tool from “Tweaking.com”, such as services, files and registry permissions, WMI and some others (I don’t remember if I did the Winsock reset…)
What solves the issue – it turns out, only temporary, is a restore of the registry. Obviously only the registry backup of the old laptop is available so I had to go through all device installation steps again (Windows does it automatically, only the wired-network interface has to be installed with manual help, using the Toshiba’s old system’s Devicestore in system32).
But after a while, the issue strikes back, again and again.
I even did a really step by step procedure when deleting old devices (and associated drivers). Making at each step a registry backup. That „worked”, and the issue was like solved, again for a few days.
Now it just came back again. I tried to trace – and will still have to – when and from what it is originated.
It’s true, I was seeing these strange SideBySide errors in the event log before – since the hard disk “migration” – but didn’t make the link because meanwhile the system still works „fine” (until not).
Now I’m here. I finally can ask this question from the community, as I look a bit helpless.
Don’t be confused about all these failure descriptions. My main question here is ONLY about those „Event ID 33 SideBySide errors” that strangely refer to an untouched (since the disk was “migrated”), never yet launched 64bit system.
I thought, as this type of error once caused me sever trouble, not being able to run a lot of programs, maybe there is a link between them and the OS “migration” into the new hardware (perhaps Windowswinsxs corruption) and also those annoying events that I described.
As I made, during the last repeated “step by step” new devices installation process and old device cleanup, some registry backups. If for example the last one get restored, the system can be used again. But then… it’s only a question of time, that it starts over.
It has to be added, that I had these two Windows installation on separate partitions without this problem, that only occurred after putting the disk and OS into its new hardware environment (while Windows installed all alone quite all the new needed drivers, but the wired network interface.)
