Import-CMDriver fails with "Import-CMDriver : Invalid object path "

I am attempting to use Import-CMDriver cmdlet for SCCM 2012 R2 but it fails with:

"Import-CMDriver : Invalid object path "

I can see that it is adding the driver to the catalog, but it is failing to add it to the package and I can't figure out why.  I have tried with different inf files and deleted and created different packages.  It just doesn't work.  Here is the command that I am running.  I don't see any reason why it wouldn't work.

 Set-Location abc:
    foreach($iniFile in $infFilesToDeploy){
        $cmDrivePackage = Get-CMDriverPackage -Name "PackageName"
        $cmDriverCat = Get-CMCategory -CategoryType "DriverCategories" -Name "PackageName"
        Import-CMDriver -UncFileLocation $iniFile -ImportDuplicateDriverOption AppendCategory -AdministrativeCategory $cmDriverCat -EnableAndAllowInstall $True -DriverPackage $cmDrivePackage -UpdateDistributionPointsforDriverPackage $false
As I said, it is seeing the ini file since it it importing it into the catalog.  It just won't add it to the package.  It also leaves the package in a locked state if I try to modify it after I run this command.

Anyone have any ideas why this command doesn't function?

I even tested without adding to a package:

Import-CMDriver -UncFileLocation "\\abe\drivers$\test\Display.Driver\nv_disp.inf"

I get the same error message about invalid object path.  It still adds the driver to the driver catalog, but displays this error message.  Seems like a bug here.  Anyone else able to add drivers using this cmdlet?

I am running this on Windows 8.1.  I also tried it on the SCCM server running Server 2012 and I get the same error.

Thank you for your time.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

gacusAuthor Commented:
If I enable -verbose, I can see this WQL query is failing:

VERBOSE: Executing WQL query: Select CTC.CI_ID,CTC.ContentID From SMS_CIToContent As CTC Join SMS_Driver As DR On

Seems to be a bug....
gacusAuthor Commented:
SCCM version 5.0.7958.1303
gacusAuthor Commented:
This was a confirmed bug my MS.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Applications

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.