Since you're not getting a BSOD or having a problem finding the i8042prt.sys and intelide.sys files and your error is entirely different then the OP of the thread you just posted to you should create you own discussion thread.

Files in the driver.cab file are older then the sp2.cab file for the same reason that files in the sp2.cab file are older then the files in the sp3.cab file.

I assume what you're calling "the patch" is the .cmd and .reg files in the .zip file I attached to one my firts reply in this thread and if so let me sat this about the .cmd script. It works like this...

It looks at the source location for sp3.cab, sp2.cab and driver.cab in that order which is newest to oldest and sets the firts one it finds in that order at the source for the i8042prt.sys and intelide.sys files . If the is the target files i8042prt.sys and intelide.sys do not already exist at the target destanation then they are expanded from the target source to the target destination.

So if the target already existed then it doesn't be overwritten and while I thought about that when I quiclky wrote the script, that was really ment just to help the person I was replying to, I didn't think it would be an issue although anything is possable.

So my suggestion is to look at the properties of the files manually any insure that the lasest version avalable from the source exist at the destanation.

By default that would be:

"%SystemRoot%" normally is "C:\WINDOWS"

Source: i8042prt.sys and intelide.sys in...

"%SystemRoot%\Driver Cache\i386\sp3.cab"
"%SystemRoot%\Driver Cache\i386\sp2.cab"
"%SystemRoot%\Driver Cache\i386\driver.cab"

Destination:

%SystemRoot%\system32\drivers

I do not know the absolutest answer to that and as a rule unless a newer version explicitly and specifically address an issue I'm of the school that I do not upgrade until I exhaust all other possibilities.

Sorry you're having a problem but I'm just a Product User not a VMware Employee so I'm not being paid to deal with someones anger.

Any news on this issue??. ty ty

This thread was started by VirtualWolf and jim.gill's reply was marked as correct and VirtualWolf replied "...and it's all working fine." and marked the thread as answered so therefore it has been answered and correctly at that!

If you're experiencing a issue it doesn't necessarily mean it is exactly the same as the person who started the thread nor does it mean that the solution or information presented in this thread will resolve your issue as well.