Impact of uiaccess = true on dlls?

Vishnu Gopalakrishnan 126 Reputation points
2021-09-29T13:54:26.643+00:00

We are planning to update an Exe to uiaccess = true and moving to the secure location.

a. Is it required to move the dependent dlls too?
b. Did we need to sign and create uiaccess = true manifest for these GUI dlls?

Windows Presentation Foundation
Windows Presentation Foundation
A part of the .NET Framework that provides a unified programming model for building line-of-business desktop applications on Windows.
2,678 questions
Windows App SDK
Windows App SDK
A set of Microsoft open-source libraries, frameworks, components, and tools to be used in apps to access Windows platform functionality on many versions of Windows. Previously known as Project Reunion.
728 questions
Windows API - Win32
Windows API - Win32
A core set of Windows application programming interfaces (APIs) for desktop and server applications. Previously known as Win32 API.
2,427 questions
Windows 10 Security
Windows 10 Security
Windows 10: A Microsoft operating system that runs on personal computers and tablets.Security: The precautions taken to guard against crime, attack, sabotage, espionage, or another threat.
2,760 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. RLWA32 40,656 Reputation points
    2021-09-29T14:48:58.197+00:00

    a. Yes, you should move dependent dlls to the secure location. Otherwise, the UIAccess application would be subject to DLL hijacking.

    b. uiaccess = true relates to a process. It has no meaning for a DLL. In my quick and dirty test on Win 10 21H1 the system permitted loading an unsigned dll into a UIAccess enabled process.