File copying works in Win10 but not in Win11

Question

I have Intune managed computers and I am packaging simple Win32 app where I copy .exe file from package root to Public Desktop. It is Teamviewer app executable without installation process, a quick launcher basically. The challenge is, that copying works perfectly fine in Windows 10 machine, but not in Windows 11.

My powershell command looks like: *Copy-Item $PSScriptRoot\TeamViewerQS.exe -Destination $Env:Public\Desktop -Force -Verbose
*
I also tried cmd: xcopy TeamViewerQS.exe %Public%\Desktop

So Both fails from Intune Win32 app, but If I try same manually on Windows 11, I also can do the copying.

Answer 1

@Pavel Yannara Mirochnitchenko, Thanks for posting in Q&A. From your description, it seems the PowerShell command we deployed via win32 is working on windows 10 but not windows 11. If there's any misunderstanding, feel free to let us know.

To clarify our issue, please check the following information:

1. Did it affect all the windows 11 devices? How did we configure "install behavior" on the win32 app?
2. If the win32 app is installed under system account, to manually test it, we use PsExec to check if the PowerShell script can be run without user interact successfully. Could you confirm if we install the app under system account and if the manually test is run under PsExec?

https://learn.microsoft.com/en-us/sysinternals/downloads/psexec

3. Check the IntuneManagementextension.log to see which phase it is failed.

https://call4cloud.nl/2021/05/imecache-attack-of-the-cleaner/

Please check the above information and if there's any update, feel free to let us know.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Hi. Thank you for your question and reaching out. I’d be more than happy to help you with your query.

There are a few reasons why your Win32 app package may not be copying the executable file to the Public Desktop on Windows 11 machines when it works on Windows 10 machines:

1. Permission issues: Windows 11 has stricter security measures in place, which may prevent the package from copying files to certain locations without the proper permissions. Make sure that the app has the necessary permissions to copy files to the Public Desktop.
2. File system redirection: Windows 11 has introduced a new feature called file system redirection, which redirects access to certain files and folders to another location. This may prevent the package from finding the Public Desktop folder in its expected location.

In addition, it's likely that the issue you're experiencing is related to changes in the operating system's security settings or file system structure between Windows 10 and Windows 11. In Windows 11, the Public Desktop folder may be located in a different location or have different permissions than in Windows 10.

One solution to this issue would be to use the Intune Management Extension to deploy the Teamviewer app executable to the appropriate location on Windows 11 machines. The Intune Management Extension allows you to run scripts and other commands on managed devices, which would allow you to copy the executable to the correct location on the target machine.

Another solution would be to configure the Intune app deployment with the correct path of the folder where you want to copy the Teamviewer executable.

You can also check the event viewer for any error related to the copy action.

If the reply was helpful, please don’t forget to upvote or accept as answer, thank you.

Answer 3

Double post

Answer 4

In my lab, same package works for Windows 11 as well :D

I will re-import the win32 package in the problematic enviroment and see if that will work out then.

Answer 5

@Crystal-MSFT I re-created new intunewin without changes and it worked...