Home

Updates Error in Windows Admin Center

%3CLINGO-SUB%20id%3D%22lingo-sub-216068%22%20slang%3D%22en-US%22%3EUpdates%20Error%20in%20Windows%20Admin%20Center%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-216068%22%20slang%3D%22en-US%22%3E%3CDIV%20class%3D%22sme-icon%20sme-icon-size-md%20sme-position-flex-none%20alert-icon%20sme-icon-error%22%3EI've%20successfully%20installed%20Windows%20Admin%20Center%201804%20in%20our%20Environment.%3C%2FDIV%3E%3CDIV%20class%3D%22sme-icon%20sme-icon-size-md%20sme-position-flex-none%20alert-icon%20sme-icon-error%22%3EMost%20all%20of%20the%20functionality%20works%2C%20with%20the%20exception%20of%20Updates.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%20class%3D%22sme-icon%20sme-icon-size-md%20sme-position-flex-none%20alert-icon%20sme-icon-error%22%3EWhen%20it%20tries%20to%20enumerate%20updates%2C%20it%20fails%20with%20the%20following%3A%3C%2FDIV%3E%3CDIV%20class%3D%22sme-position-flex-auto%20alert-content%22%3E%3CP%20class%3D%22sme-screen-reader%22%3EError%3C%2FP%3E%3CP%3E(1)%20RemoteException%3A%20An%20object%20at%20the%20specified%20path%20C%3A%5CUsers%5CJ6D1D~1.BAI%20does%20not%20exist.%20(2)%20RemoteException%3A%20An%20object%20at%20the%20specified%20path%20C%3A%5CUsers%5CJ6D1D~1.BAI%20does%20not%20exist.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20had%20other%20users%20try%20%26amp%3B%20fail%20with%20similar%20error%20messages%20for%20the%20user%20path%2C%20however%2C%20these%20are%20not%20our%20actual%20user%20profiles%2C%20or%20standard%20user%20names%20that%20we%20login%20with.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20I%20rename%20user%20profile%20folder%20on%20the%20system%20~%20example%20(C%3A%5Cusers%5Cusername.old)%20create%20the%20path%20in%20question%2C%20it%20is%20able%20to%20enumerate%20the%20updates%20through%20WAC.%3C%2FP%3E%3CP%3EI%20don't%20believe%20I%20should%20have%20to%20rename%20all%20the%20user%20profiles%20on%20the%20systems%20I%20am%20connecting%20to%20in%20order%20to%20get%20this%20to%20work...%3CBR%20%2F%3E%3CBR%20%2F%3EDoes%20anyone%20else%20have%20this%20issue%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-302731%22%20slang%3D%22en-US%22%3ERe%3A%20Updates%20Error%20in%20Windows%20Admin%20Center%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-302731%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can%20confirm%2C%20we%20have%20exactly%20same%20problem.%20As%20a%20workaround%2C%20it%20seems%20you%20can%20create%20new%20AD%20account%20without%20a%20%22.%22%20in%20the%20username%20and%20then%20Updates%20also%20work.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20mean%20if%20your%20current%20account%20(the%20one%20you%20use%20when%20you%20connect%20to%20WAC%20via%20web%20browser)%20is%20admin.john.doe%20and%20you%20create%20a%20new%20AD-account%20adminjohndoe%20with%20same%20permissions%2C%20adminjohndoe%20wont%20generate%20that%20error.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20yeah%2C%20really%20annoying.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Jared Bailey
New Contributor
I've successfully installed Windows Admin Center 1804 in our Environment.
Most all of the functionality works, with the exception of Updates.

When it tries to enumerate updates, it fails with the following:

Error

(1) RemoteException: An object at the specified path C:\Users\J6D1D~1.BAI does not exist. (2) RemoteException: An object at the specified path C:\Users\J6D1D~1.BAI does not exist.

 

I've had other users try & fail with similar error messages for the user path, however, these are not our actual user profiles, or standard user names that we login with.

 

When I rename user profile folder on the system ~ example (C:\users\username.old) create the path in question, it is able to enumerate the updates through WAC.

I don't believe I should have to rename all the user profiles on the systems I am connecting to in order to get this to work...

Does anyone else have this issue? 

 

1 Reply

Hello,

 

I can confirm, we have exactly same problem. As a workaround, it seems you can create new AD account without a "." in the username and then Updates also work.

 

I mean if your current account (the one you use when you connect to WAC via web browser) is admin.john.doe and you create a new AD-account adminjohndoe with same permissions, adminjohndoe wont generate that error.

 

But yeah, really annoying.