How do I resolve newer component version conflict.

G

Guest

I just updated my XPe Tools and Database to SP2. I have a configuration that
has been working on a machine prior to the upgrade. I have decided to modify
the configuration by putting in Background Disk Defragmentation Disable and
EWF omponent features. I then got a conflict error message during Dependency
Check saying "Standard PC [Version 5.1.2600.2180, R2890] conflicts with some
other components. After removing the components I added, the message still
remained meaning they were not the cause of the conflict. I later found out
that the version in the ol working configuration is 'Standard PC [Version
5.1.2600.1106, R1507]'. How do I revert back to this componenthat, I mean
excluding the later component version. T
Thank you.
 
E

Ethan Chen

The "Standard PC" component conflict problem happened should be more than
one HAL components added into your configuration. The component version
should not be the root cause.

Best Regards,
Ethan Chen
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Bad dependency ".NET Frame. 1.1" to "Windows Logon" - (Session Manager 2
Problem with SmartUpgrade Component from xpefiles.com 3
dependency errors 2
XPECMD -- using deptree to find which components need component X 4
dependency errors 4
ACPI, EWF NTLDR and NTLDR conflict 5
Issue with Feature Pack2007 8
.NET Framework 2.0 component 11

Top