ADSI failing on missing WOW currentVersion registry key

Fixed, not yet flighted Issue #6638841

Details

Created
Feb 22, 2016
Privacy
This issue is public.
Reports
Reported by 11 people

Sign in to watch or report this issue.

Steps to reproduce

URL:

Repro Steps:

Sample project attached.

See the thread for details: https://connect.microsoft.com/IE/feedback/details/1904887/windows-10-insider-preview-build-10565

On the insider preview build this failed with Unhandled Exception: System.IO.FileNotFoundException: The system cannot find the file specified.
at System.DirectoryServices.Interop.UnsafeNativeMethods.IAds.GetInfo() at System.DirectoryServices.DirectoryEntry.RefreshCache() at System.DirectoryServices.DirectoryEntry.FillCache(String propertyName) at

Both installations are virtual machines, no domain name, brand new installs, with nothing on them but VS 2015 and testing above code.

Expected Results:

this is supposed to work and it worked up until build 10565

Actual Results:

Dev Channel specific:

Yes

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Mara P.”

      Changed Assigned To to “Vivek M.”

      Changed Assigned To from “Vivek M.” to “Lee C.”

    • Hi,

      I am also facing the same issue. I think this is not related to browser.
      We have windows application and we are trying to retrieve the security groups for the UserPrincipal. This is working on OS version= 10240 and failed on Version= 10586
      The workaround of adding strings (RegisteredOwner and RegisteredOrganization) to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion is working but which is not feasible in our case as our app gets deployed on more than thousands of machines. So it is not preferred. Please Update after fix ASAP.

      Below is the sample code :
      var user = UserPrincipal.FindByIdentity(userDomain, userName);
      if (user != null)
      {
      var groups = user.GetAuthorizationGroups(); // This line throws Exception
      }

      Exception :
      System.IO.FileNotFoundException: The system cannot find the file specified.

      at System.DirectoryServices.Interop.UnsafeNativeMethods.IAds.GetInfo()
      at System.DirectoryServices.DirectoryEntry.RefreshCache()
      at System.DirectoryServices.AccountManagement.PrincipalContext.DoMachineInit()
      at System.DirectoryServices.AccountManagement.PrincipalContext.Initialize()
      at System.DirectoryServices.AccountManagement.PrincipalContext.get_QueryCtx()
      at System.DirectoryServices.AccountManagement.Principal.FindByIdentityWithTypeHelper(PrincipalContext context, Type principalType, Nullable1 identityType, String identityValue, DateTime refDate) at System.DirectoryServices.AccountManagement.Principal.FindByIdentityWithType(PrincipalContext context, Type principalType, IdentityType identityType, String identityValue) at System.DirectoryServices.AccountManagement.GroupPrincipal.FindByIdentity(PrincipalContext context, IdentityType identityType, String identityValue) at System.DirectoryServices.AccountManagement.AuthZSet.get_CurrentAsPrincipal() at System.DirectoryServices.AccountManagement.FindResultEnumerator1.get_Current()
      at System.DirectoryServices.AccountManagement.FindResultEnumerator1.System.Collections.IEnumerator.get_Current() at System.Linq.Enumerable.d__921.MoveNext()
      at System.Linq.Enumerable.WhereSelectEnumerableIterator2.MoveNext() at System.Collections.Generic.List1.InsertRange(Int32 index, IEnumerable`1 collection)
      at MSITWin8.Deployment.Core.Helpers.SecurityGroupHelper.ResolveUsersGroups()
      — End of inner exception stack trace —

    • I am dealing with the exact same issue. As Pravin said, the registry hack solution works, but is not workable for mass deployment. Please fix, and in the meantime, inform the development community as to why the registry hack solution even works at all.

    • We too are having this issue. Our installer started failing after upgrading to the 10586 build. Adding the registry keys as suggested allows working around the problem, however that is not an acceptable long term solution. We shouldn’t have to be adding OS-owned registry keys as part of our install process.

    • Microsoft Edge Team

      Changed Assigned To from “Lee C.” to “Travis Q.”

      Changed Status to “Confirmed”

      Changed Title from “Windows 10 - insider preview build 10565” to “ADSI failing on missing WOW currentVersion registry key”

      Changed Assigned To from “Travis Q.” to “IE S.”

      Changed Status from “Confirmed” to “Fixed, not yet flighted”

    • Why is this issue tracked here for Edge? Seems to be more related to Windows Operating system in general!

    • Also being bitten by this issue; we’re developing a 64 bit MSI installer and adding registry keys to work around this seems very intrusive.

    • This is a known issue that we are tracking internally, but according to input from other team members this has been fixed in builds 14268 and higher. Please feel free to reactivate if you see this as a problem we should investigate.

      All the best,
      The MS Edge Team

    You need to sign in to your Microsoft account to add a comment.

    Sign in