Damnation Posted August 4, 2017 Posted August 4, 2017 Out of curiosity I was looking at windows 10 ntoskrnl with dependency walker and noticed all these ext-ms-win dll files it depends on. I noticed however that the files do not seem to exist in c:\windows\system32 (or sysWOW64) - So where are these dependencies actually located? 2
HarryTri Posted August 4, 2017 Posted August 4, 2017 Have you turned the showing hidden files option on?
HarryTri Posted August 4, 2017 Posted August 4, 2017 Strange, they are present in Windows 8 that I am running, and since ntoskrnl.exe depends on them they must still be present in Windows 10 too.
Damnation Posted August 4, 2017 Author Posted August 4, 2017 grab a windows 10 ISO and install in a VM, you can see they're absent. 1
UCyborg Posted August 4, 2017 Posted August 4, 2017 (edited) I don't see them neither. Maybe those DLL names internally resolve to something else? I ran a search and haven't found them anywhere in Windows folder. Edited August 4, 2017 by UCyborg
Damnation Posted August 5, 2017 Author Posted August 5, 2017 1 hour ago, UCyborg said: I don't see them neither. Maybe those DLL names internally resolve to something else? I ran a search and haven't found them anywhere in Windows folder. I don't know how to figure out what it resolves to. Anyone know how to do that? 1
jaclaz Posted August 5, 2017 Posted August 5, 2017 (edited) Broken google? https://ofekshilon.com/2016/03/27/on-api-ms-win-xxxxx-dll-and-other-dependency-walker-glitches/ Welcome to the wonderful world of API sets (whatever they are besides being an added layer of complexity). Use the page above to get to Geoff Chappel's site with the full list and a nice explanation (or copy and paste the following). http://www.geoffchappell.com/studies/windows/win32/apisetschema/index.htm?tx=3 http://www.geoffchappell.com/studies/windows/win32/apisetschema/api/index.htm jaclaz Edited August 5, 2017 by jaclaz 1
Damnation Posted August 5, 2017 Author Posted August 5, 2017 5 hours ago, jaclaz said: Broken google? https://ofekshilon.com/2016/03/27/on-api-ms-win-xxxxx-dll-and-other-dependency-walker-glitches/ Welcome to the wonderful world of API sets (whatever they are besides being an added layer of complexity). Use the page above to get to Geoff Chappel's site with the full list and a nice explanation (or copy and paste the following). http://www.geoffchappell.com/studies/windows/win32/apisetschema/index.htm?tx=3 http://www.geoffchappell.com/studies/windows/win32/apisetschema/api/index.htm jaclaz Cool, Thanks very much! 1
Damnation Posted August 12, 2017 Author Posted August 12, 2017 56 minutes ago, Dibya said: They are hidden system files . It's more complex than that apparently 1
UCyborg Posted August 12, 2017 Posted August 12, 2017 (edited) Not directly related to API sets, but regarding MS's moving functionality around, we also have *base.dll DLLs, eg, winmmbase.dll, combase.dll, etc. kernelbase.dll was already in Win7, those two and some others came later. Edited August 12, 2017 by UCyborg
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now