Workfoldersystemtray.exe - This application could not be started

[karims]

We have deployed Work Folders for Windows 7 for several thousand computers.

About 150 of them have it deployed through GPO (only as optional). Every time background policy refresh runs it promps about 4 of them with the error message below.

It also happens when opening Work Folders from Control Panel. Im still able to fully configure Work Folders for the user but the message pops up every time they use it through Control Panel so I'm seeking a solution to the problem.

All of the domain users are in the local Administrators group on their computer.

When clicking Yes I'm directed to this page:

https://support.microsoft.com/kb/2715633

Tried so far:

• Reinstalling .NET Framework
• Reinstalling Work Folders patch (KB2891638)

Anyone seen this error before? I went through the Event log for Work Folders but didn't find anything related to the error message, also had a look on the application event log.

 

[JaneYan]

Hi,

I worked on this application, and like to help with the issue. From the message box, it looks like the system tray is not starting correctly. Let me see what additional logging you can help me to collect to investigate this.

Thanks,

 

[JaneYan]

Hi,

I'd like to get additional tracing to help with the diag:

To collect Work Folders System Tray logs:
· Enable logging by running comand:
reg add "HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\WorkFolders\UserState" /v SystemTrayEnableTracing /t REG_DWORD /d 1 /f
· After bug reproduction, collect logs from:
%USERPROFILE%\AppData\Local\WorkFolders\SystemTray

You can send the logs to me directly at jianyan at microsoft.

Thanks,
Jane

 

[karims]

Thank you Jane, I'll get back to you as soon as possible!

 

[karims]

I added the DWORD value to registry and performed a reboot, I then reproduced the bug several times but nothing were logged, also tried creating the folder manually to see if that would make any difference, user had all permissions to the folder but nothing were logged.

 

[JaneYan]

Thanks for trying, let me do some look up.

 

[JaneYan]

One more question, what version of .net do you have on those computers?

 

[karims]

One more question, what version of .net do you have on those computers?

Microsoft .NET Framework 4.5.2, version 4.5.51209 and .NET Framework. 3.5 should be installed aswell in the Add or Remove Windows Features list.

 

[karims]

Update: Deployed Work Folders as enforced for another 70 users today. Still haven't gotten any feedback on this error from the users, but I will give you an update if I hear anything. They have approximately 30 Windows 7 computers and the patch has previously been released.

 

[JaneYan]

I'm still looking for info on how to collect the trace for that particular error, it seems coming from the systray.

Just curious, why do you choose to deploy Work Folders with automatic setup? vs having user manually setup so they can choose when to setup?

Thanks,
Jane

 

[karims]

Thank you for looking into this Jane!

The reason for deploying automatically is because I think the user experience is better when it's already deployed when they receive the information that they have a new feature available with a user guide, instead of having them manually deploy it.

I also don't see any reason for our users not to have it. There's approximately 800-900 users where we configured it as optional because they don't need it that as much as the others.

 

[yvonneb]

I realize this thread is old, but I just spend a week uninstalling and reinstalled different versions of .NET to try to find the answer... in the end it was an easy fix, but nobody on the web has posted the answer yet ...
SOLUTION:
Change .netv2.0 to run in 64 bit mode instead of 32 bit.
1.Navigate to C:\Windows\Microsoft.NET\Framework64\v2.0.50727 (yes, workfolders seems to use version 2)
2.ldr64.exe query – This will return 0x0000000 – if so then the 32 bit mode is running, this is incorrect
3.ldr64.exe set64 – This will change the value to 0x0000001.

More Info:
To run 32 Bit mode (if you have other apps that need 32 bit):
C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Ldr64.exe SetWow
To run 64 bit Mode:
C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Ldr64.exe Set64