Issues uninstalling useing device management (Intune) #1342
Replies: 3 comments
-
|
We unfortunately do not have any experience with Intune. The above behavior is however expected, as the setup bundle contains resp. installs the appropriate MSI depending on the platform architecture ‒ thus, if you only uninstall the MSI, the bundle itself will still appear as being installed. You should directly uninstall the bundle itself, then everything should be correctly removed from the system. The potential issue with the return codes is not known to us, it could however be caused by various factors. We intend to update the installers to the latest WiX Toolset version which might resolve the issue, but had unfortunately thus far not had the time to tackle that task. |
Beta Was this translation helpful? Give feedback.
-
|
Ok. Since you don't have access to Intune I have done some testing on the device manually using the command promt. Uninstalling using Windows Settings Installed Apps (Add/Remove programs).
Uninstalling using msiexec /x "{B0009434-560A-434A-A6AA-061F0F132F90}" /qn
Uninstalling using the same SetupBundle.exe used by Add/Remove programs stored in C:\ProgramData\Package Cache{9a409bb3-e52a-47ed-b5be-98ee6809a1ef}
So the added arguments have no effect what so ever to the behaviour of the process. This is contra intuitive, as running SetupBundle.exe /uninstall should start the uninstall process without any confirmation dialog box, and SetupBundle.exe /uninstall /qn should uninstall silently. I believe that if /uninstall /qn arguments worked, the issue we see in intune would also be resolved. As it stands now, SEB cannot be silently uninstalled using any management solution. Uninstalling using Add/Remove Programs is not an option as students arent local admin on their devices. PS: I must have made an mistake above when I wrote that C:\ProgramData\Package Cache{9a409bb3-e52a-47ed-b5be-98ee6809a1ef}\SetupBundle.exe /uninstall uninstalled SEB but leaving the uninstaller running forever. The uninstall runs forever, but the app isn't removed. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, so I think I have found a solution to this issue. I looked into the SetupBundle.exe some more, and figured that I could use;
This successfully uninstalled Safe Exam Browser with this uninstall command triggered from Intune. And yes, I found that this was a little strange as I'm under the impression this is a Wix Burn, not Install Shield, so I would assume /S etc. wouldn't have any effect. But I'm not a developer, I've just spent a few days trying to read up on the subject. PS: The full string for version 3.10.1.864 is;
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
This one is a bit unusual. When deploying Safe Exam Browser (SEB), I currently use the .EXE installer because it includes prerequisites like .NET and Visual C++ Redistributable. However, I still use the MSI for detection and the uninstall string msiexec /x "{B0009434-560A-434A-A6AA-061F0F132F90}" /qn
This matches the uninstall command listed in the registry under:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{B0009434-560A-434A-A6AA-061F0F132F90}
The issue is that after running this uninstall, SEB is only partially removed. The registry entry disappears, but SEB still shows under Installed Apps, and I need to click Uninstall again to fully remove it.
When uninstalling manually from Installed Apps, Windows uses:
C:\ProgramData\Package Cache{9a409bb3-e52a-47ed-b5be-98ee6809a1ef}\SetupBundle.exe /uninstall
However, triggering this through Intune (Company Portal) behaves oddly—the uninstall runs indefinitely. If I double-click the .exe, I get a dialog box with an Uninstall button. When uninstalling via Windows Apps, /uninstall is added, but the user still sees the dialog box. I assumed the app might not support /qn or /quiet, so I removed /qn expecting the dialog to appear when uninstalling via Company Portal. Instead, the uninstall still runs forever with no dialog, although the app is removed.
My guess is that the installer doesn’t return proper exit codes, so Intune can’t detect completion. I’m not a developer, so I’m unsure how this works internally.
Has anyone else experienced this with Intune? Do you have a solution—or does it work fine for you?
Beta Was this translation helpful? Give feedback.
All reactions