[PSADT.UiAutomation] does not contain a method named 'SetProcessDPIAware' about psappdeploytoolkit HOT 11 CLOSED

i have made sure i am using the latest 3.10.0 files everything was moved to a new folder once downloaded then deploy.ps1 edited

from psappdeploytoolkit.

Same issue here. Running inside a Hyper-V virtual machine, if that makes any difference. None of the displays involved are high resolution - dual monitors with 1920x1080p resolution.

from psappdeploytoolkit.

Please could you both confirm if you were using:

• Old style Powershell console
• Powershell ISE
• Windows Terminal
• VSCode
• Something else?

Also, does it work via Deploy-Application.exe?

from psappdeploytoolkit.

Also, if you have the unofficial PSADT PowerShell module installed, can you try uninstalling it in case it’s causing a conflict?

from psappdeploytoolkit.

I have replicated in testing by doing either of the following:

• Run PSADST 3.9.3 or earlier, then try to run 3.10.0 in the same PowerShell session

• Install unofficial PSADT module 3.9.3 or earlier, then run Import-Module PSADT (or trigger import by running one of the PSADT commands) before running 3.10.0

These are not really supported scenarios, so I doubt anything will be implemented to resolve this. The solution is simply to always ensure you are running in a clean Powershell environment; deploying your application via Deploy-Application.exe should accomplish this. I'll close this for now, but it it's affecting actual deployments, please comment with further info and we can re-open and investigate.

One possible solution is to change the namespace whenever we introduce a breaking change or new class in AppDeployToolkitMain.cs, e.g:

namespace PSADT_v3.10.0

[System.Void][PSADT_v3.10.0.UiAutomation]::SetProcessDPIAware()

But that isn't a common convention, involves more maintenance, and looks ugly.

from psappdeploytoolkit.

@DanGough, late in replying, but you're absolutely right - I had an old version of the module installed. Uninstalling it cleared up the issue. Thanks.

from psappdeploytoolkit.

Same as Bug #940. Still having the same Problem in v3.10.1. Reproducable Problem and no other solution found than removing the Line "[System.Void][PSADT.UiAutomation]::SetProcessDPIAware()"

Nevers logged on that client before, so no Userprofile existed where somehting might be cached.

Running directly from Powershell included in Windows 10 22H2.

Please reopen the Bug

from psappdeploytoolkit.

@ClientSupportCDB please can you check if you have the PSADT PowerShell module installed?

from psappdeploytoolkit.

these are the only ones i have installed

Get-InstalledModule

Version Name Repository Description

2.19.0 Microsoft.Graph.Authentication PSGallery Microsoft Graph PowerShell Authentication Module.
2.19.0 Microsoft.Graph.Devices.Corporat... PSGallery Microsoft Graph PowerShell Cmdlets
2.7.0 Microsoft.Graph.Groups PSGallery Microsoft Graph PowerShell Cmdlets
6.1907.1.0 Microsoft.Graph.Intune PSGallery PowerShell SDK for Microsoft Intune Graph API
0.9.0.6 PendingReboot PSGallery Module to detect Windows OS pending reboots.
5.6 WindowsAutoPilotIntune PSGallery Sample module to manage AutoPilot devices using ...

is there anything you would like me to try?

from psappdeploytoolkit.

I've run into same issue with latest 3.10.1 standalone package on Windows 10 22H2 and no PSADT module installed. I have to comment out this line [System.Void][PSADT.UiAutomation]::SetProcessDPIAware() in AppDeployToolkitMain for it to run.

from psappdeploytoolkit.

Make sure you've updated all the files in the toolkit folder, particularly the .cs file in addition to Main. Also, if you execute a 3.9 or older deployment script then try to run a 3.10.1 one from the same Powershell session, I would expect this error.

from psappdeploytoolkit.