I'll start with the 'pre
' installation requirements for KB2483614
This is similar to OS detection, it is required by this particular update so the proper version of RDC7 is updated
- here's the code from the update.
GreatOrEqualOp = CheckFilever, System32.files, mstscax.dll , >= , 6.1.7600.16385
The only difference is I used mstsc.exe. Notice this is also the version number from the original RD7 update KB969084. With the correct OS and Component version in place, this update should get flagged for installation. That's why the other update didn't install - wrong RDC version. So the short answer is 'Yes' - for this particular update it is expecting a minimum version of RDC - 6.1.7600.16385
How I was wanting you to confirm this was by removing all 'post' install checks from the apm file - .reg, .cat, and .exe checks. If the apm is correct this update should once again be selected for install (black) when you start AutoPatcher. I hope it is. Now, you can leave the check in place (in the apm), we know it works.
'Pre' install check example:
' installation checks. One at a time, and only one at a time. Confusing huh. Just like you said above, why add more, the detection already works. True, on your system, but on another system it may not be the reg entry, it may be the .cat, & .exe combo. That is why you have to test each one - one by one. Test#1 - .reg, does it work? remove. Test#2 - .cat, does it work? remove. Test#3 - .exe, does it work?
The file detections have to be a pair but I still like to test individually first.
The point is to determine if each one is enough to detect the update as installed. If your first detection (registry) works, you can put anything after it (file(s)) and the update will still be blue on the tested system. Btw, this is what Cristiano was doing for you by testing all your fixpack entries - yes it takes some time.
If I was at my machine that has my XP SP3 VM on it I would test the detections. Really, it takes maybe 5 minutes to 'cut', 'copy', 'paste' the various detections to and from the apm file, fire up AutoPatcher - test - edit apm etc. I thought you and Cristiano covered this already with the fixpack stuff?
If you can't or wont do it that's fine just let me know. It is true that either the registry or .cat detections are adequate but I simply wanted to test the .exe detection on it's own as well - just like I have it in the apm, so no, you don't need to change anything - FileVersion=>6.1.7600.16722
was what I wanted to test.
Hopefully each detection will work, each time marking the update Blue
- if so... The whole Shebang: