Driver Component Confusion with Windows Embedded

I need some help from someone familiar with Windows Embedded Target Designer and Component Designer:

On my Windows Embedded image I have two driver components that are "conflicting", but not for IO reasons.

The first driver component is the touchscreen driver that includes its own serial port enumerator called pmserenum.sys.

The second driver component, which is for a PCI serial port controller, normally uses Microsoft's default serenum.sys serial port enumerator. However, after FBA, for some reason it's using the touch-screen's pmserenum.sys file instead, and the serial ports don't work.

How can I force the serial port driver component to use serenum.sys instead of pmserenum.sys? It works perfectly if the touchscreen driver (and therefore pmserenum.sys) isn't present.

Screenshots attached:

http://img59.imageshack.us/img59/5615/badbehaviour.png - this is how it looks after FBA

http://img59.imageshack.us/img59/4716/goodbehaviour.png - this is how it should look

Can you just right-click the device in device manager, choose 'update driver', and then manually specify the correct driver? Instead of letting it autodetect which driver.