We've run into multiple WinXPProSP3 computers generating error code 16389 when trying to run a TS.  After searching on Google, we found this, 

http://blogs.technet.com/b/smsandmom/archive/2007/10/29/sccm-2007-task-sequence-fails-drive-letter-not-displayed.aspx

, which led to another article to modify a RegKey,  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318} , to add a key of UpperFilters, with a value of PartMgr.  The key WAS missing on the machines with the error, and, adding that key and value DOES fix the problem.  This key and value seem to be default for the OS.

However, searching Google for that RegKey has a LOT of suggestions to delete that key and value, due to issues with USB Thumbdrives and iPods not being seen when plugged in--so, it seems that there may be a conflict.

Does anyone know of a fix for Error 16389 without having to add that key, if it's going to cause other problems?

Thanks.

• Moved by Michael W [MSFT] Thursday, December 22, 2011 9:34 PM OSD handles Task Sequence (From:Configuration Manager Software Distribution)

Are you actually experiencing the issue being described in that post or are you just getting the same error code?

That error code is a generic error and can mean a lot of different things.

Hi,

Will you please past the detailed errors in the smsts.log?

From your description your are using TS to install software right?

If so you should first make sure this software package meats the following requirement when it was deployed through TS:

• this program can be installed under local system account.
• this program can be installed without any user interaction (such as: press next button).
• this program will not force computer reboot, it allows sccm ts to manage the reboot.

If your OSD TS return 16389 exit code, you can try to change the volume license keys. Because once i have seem this error and it was solved by changing the volume license key.

Hope this will help.

Thanks

• Marked as answer by Robinson Zhang Friday, December 30, 2011 10:14 AM

I know this is all a bit late, but just for future reference. The exeit code 16389 can also mean the package program did not have "Allow this program to be installed from the Install Software task sequence without being advertised" enabled.

This can happen if the TS references an old revision of an application which no longer exists. Workaround is to remove the application from the TS and add it back.

Hi Guys

having the same issue with installing applications with task sequence

the sequence is:

• install application 1
• restart
• Install application 2
• restart
• Install application 3
• restart

my problem is that I get this error on machines randomly. each time the error 16389 can be on a different app (it's not on the same app all the time)

the deployment also succeed on some of the clients so I can't seem to find the real problem here...

The applications are marked to be able to install through Task Sequence.

please help