SetThreadDesktop function
Applies to: desktop apps only
Assigns the specified desktop to the calling thread. All subsequent operations on the desktop use the access rights granted to the desktop.
Syntax
BOOL WINAPI SetThreadDesktop( __in HDESK hDesktop );
Parameters
- hDesktop [in]
-
A handle to the desktop to be assigned to the calling thread. This handle is returned by the CreateDesktop, GetThreadDesktop, OpenDesktop, or OpenInputDesktop function.
This desktop must be associated with the current window station for the process.
Return value
If the function succeeds, the return value is nonzero.
If the function fails, the return value is zero. To get extended error information, call GetLastError.
Remarks
The SetThreadDesktop function will fail if the calling thread has any windows or hooks on its current desktop (unless the hDesktop parameter is a handle to the current desktop).
Warning There is a significant security risk for any service that opens a window on the interactive desktop. By opening a desktop window, a service makes itself vulnerable to attack from the logged-on user, whose application could send malicious messages to the service's desktop window and affect its ability to function.
Requirements
|
Minimum supported client | Windows 2000 Professional |
|---|---|
|
Minimum supported server | Windows 2000 Server |
|
Header |
|
|
Library |
|
|
DLL |
|
See also
- CreateDesktop
- Desktops
- GetThreadDesktop
- OpenDesktop
- SetProcessWindowStation
- Window Station and Desktop Functions
Send comments about this topic to Microsoft
Build date: 2/3/2012
This is understated. SetThreadDesktop will fail if the calling thread has ever had a window or hook on its current desktop.
- 3/16/2010
- Blake Coverett
The first paragraph on this page says "All subsequent operations on the desktop use the access rights granted to the desktop."
This isn't very clear to me: I guess it means that any windows or hooks subsequently created by the thread are set on that desktop, but I don't understand what the "access rights granted to the desktop" are. Every desktop has a security descriptor contaning (among other things) a DACL, but it is not a security subject, it does not have a SID and does not have access rights: other ACLs in the system cannot refer to a desktop.
I would have understood that statement if it was on the CreateDesktop function's documentation: every subsequent operation on the newly created desktop uses the access rights granted to the desktop (as an object, not a subject) through the specified security descriptor.
