Runtime DLL name resolution: ApiSetSchema - Part I
blog.quarkslab.com | research | #windows | #reverse-engineering | #apisetschema | #dll | #windows-internals | #minwin
Summary
ApiSetSchema explained, part one: why Windows 7+ DLLs forward calls (Kernel32 to KernelBase) under Minwin, and how virtual DLLs map to real implementations through an early-loaded schema.
- Published
- Collected
--- id: 4590 title: "Runtime DLL name resolution: ApiSetSchema - Part I" source_domain: blog.quarkslab.com source_url: "https://blog.quarkslab.com/runtime-dll-name-resolution-apisetschema-part-i.html" published_at: "2012-04-05T22:00:00Z" tags: ["windows", "reverse-engineering", "apisetschema", "dll", "windows-internals", "minwin"] phying_url: "https://phying.com/item/4590" lang: en --- # Runtime DLL name resolution: ApiSetSchema - Part I ## Summary ApiSetSchema explained, part one: why Windows 7+ DLLs forward calls (Kernel32 to KernelBase) under Minwin, and how virtual DLLs map to real implementations through an early-loaded schema. ## Intelligence Metadata - **Sources:** blog.quarkslab.com - **Published:** 2012-04-05T22:00:00Z - **Original:** https://blog.quarkslab.com/runtime-dll-name-resolution-apisetschema-part-i.html - **Phying News:** https://phying.com/item/4590