Windows 7 computers on my domain are returning "Filename or extension too long" errors on files that were previously accessible. The filenames and extensions are not too long. When the computers are rebooted,
they fail to fully load windows and Startup Repair appears. Startup Repair does not fix the problem, and the only way to fix it is to start using "Last Known Good Configuration". This problem has spread throughout the domain to the computers, and they fail
randomly.
In the Event Log the the first symptom is usually this SideBySide error:
Log Name: Application
Source: SideBySide
Event ID: 72
Task Category: None
Level: Error
Keywords: Classic
Computer:
Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child
of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.
and then VSS returns errors similar to this:
Log Name: Application
Source: VSS
Event ID: 13
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
Volume Shadow Copy Service information: The COM Server with CLSID {e579ab5f-1cc4-44b4-bed9-de0991ff0623} and name IVssCoordinatorEx2 cannot be started. [0x800700ce, The filename or extension is too long.
]
Operation:
Instantiating VSS server
On the next reboot of the machine, the computer will fail to start. Startup repair is unable to fix the issue, and I must hit F8 and start in "Last Known Good Configuration" and the machine returns to normal.
I have no idea what is happening, and virus scans return nothing.
Thank you for your time.