Bug 15456 – sc.ini: Access denied for non-superusers on Windows 10
Status
RESOLVED
Resolution
FIXED
Severity
major
Priority
P1
Component
installer
Product
D
Version
D2
Platform
All
OS
Windows
Creation time
2015-12-16T16:18:00Z
Last change time
2016-01-18T17:24:18Z
Keywords
pull
Assigned to
nobody
Creator
david.eckardt
Comments
Comment #0 by david.eckardt — 2015-12-16T16:18:06Z
After installing DMD on Windows 10 normal users have no access permission for sc.ini. DMD's error message says that object.d wasn't found, which is very misleading.
Comment #1 by eco — 2015-12-16T19:12:36Z
(In reply to David Eckardt from comment #0)
> After installing DMD on Windows 10 normal users have no access permission
> for sc.ini. DMD's error message says that object.d wasn't found, which is
> very misleading.
Did you install it in Program Files or something like that? I can't think of any reason a regular user wouldn't have permissions. It works fine for me in Windows 10.
Comment #2 by david.eckardt — 2015-12-17T13:50:25Z
(In reply to David Eckardt from comment #2)
> This happened with the dmd-2.069.2 installer
>
> http://downloads.dlang.org/releases/2.x/2.069.2/dmd-2.069.2.exe
>
> on Windows 10 Home, using the default installation options, which install it
> in the C:\D\ directory.
Oh, my apologies. I wasn't using the latest version. Just reproduced the object.d error but my sc.ini was fine and accessible. My druntime folder was completely missing... Then I uninstalled and reinstalled several versions going back to 2.069.0 and all had weird, different files missing.
I think it might be the uninstaller is still recursively deleting things even as the installer is busy installing the new version... Very unexpected bug. I'm looking into it more.
Comment #4 by eco — 2015-12-17T21:15:59Z
Added Rainer and Martin on the CC. Assuming it's the same bug you hit, it seems you can reproduce by going through the uninstaller and installer as quickly as possible. The uninstaller "finishes" almost instantly once it gets to the RMDir /r part which makes me think it's doing the deletions asynchronously and the new files being added by the installer are subject to the delete. Very ugly bug.
One quick fix might be to rename the C:\D folder prior to deleting it. I'm unfortunately too busy at the moment to try to fix this myself but might be able to look in a couple weeks.
Yep, it's just the permissions. The other issue issue I hit in the above comments is unrelated (though still a problem). Either pull request will fix this issue.
Comment #7 by github-bugzilla — 2016-01-18T17:22:04Z