I setup a Win32 Application in my Intune as Required, then one of my AAD Joined machines got the application installed. Later I explicitly uninstalled it and now Intune's app status displays an error for that application on that device:
The application was not detected after installation completed successfully.
Couldn't detect app because it was manually updated after installation or uninstalled by the user.
Doesn't matter what I do now in Intune I cannot get the application installed on that box again, that error is still displayed. Tried to "Sync" from both - the device as well as Intune - nothing helps in terms of that application's status in Intune.
Why the Required application is not automatically installed if a user uninstalled it? I find this contradicting with the definition of Required. How do I get the application installed back via Intune without asking the user to explicitly install it?
Related
my application work by vb6.
The Error occur after install Office 2015. Before installing Office 2015 will by my program worked.
Msdbrptr.dll version 6.0.81.69 year 2018.
Run-time error '372': Failed to load control 'DataReport' from C:
WINDOWS \ SysWOW64 \ Msdbrptr.dll. Your version of the C: \ WINDOWS
SysWOW64 \ Msdbrptr.dll may be outdated. Make sure you are using the
version of the control That was provided with your application.
I delete Msdbrptr.dll then add it but same error exist.
can anyone help me ?
According to Microsoft KB 942870:
Action
You attempt to run a Visual Basic 6.0 application that contains an
ActiveX control.
Result
You receive the following error message:
Runtime Error: 372 - Failed to load control from
<control.ocx>.Your version of <control.ocx> may be outdated. Make sure
you are using the version of the control that was provided with your
application
Cause
This can occur when the user running the application is logged on
under a different user account than the user account who installed the
application, and the installation package installed the application on
a per user basis.
When an application is installed for a specific user, the COM
components referenced in the application are registered in the
HKEY_CURRENT_USER hive in the Windows registry. When an application is
installed for All Users, the registry entries are made to the
HKEY_LOCAL_MACHINE hive in the Windows registry, and all users should
be able to read these entries by default.
Resolution
Modify the installation program to install the application for All
Users.
Could someone recommend some troubleshooting tips for the Windows App Certification Kit (WACK) process when attempting to Create an App Package for the store? The app package builds fine, however, when WACK starts it immediately crashes with an "Unspecified Error".
I'm using VS Community and an Individual developer account.
I've tried uninstall WACK and re-installing, but it is integrated in VS Community, so no luck there. I have also tried side-loading the app, but the PowerScript (PS) fails. Checking the PS log it states, "The specific error text for this failure is: Unspecified error."
I had the same issue but deleting the AppPackages, bin, BundleArtifacts and obj folder before running the Store Certification fixed the issue.
We have implemented a Windows 8 app. We tested the app by sideloading on both Windows 8.1 Pro and Enterprise. The app is working as expected when both the machines are connected to the domain. If both the machines are out of the domain, the app does not work and we receive the following error ‘This app can’t open. There’s a problem with app. Contact your system administrator about repairing or reinstalling it’. Also, in the event log the following error was displayed ‘Activation of the app 589f3680-7094-4066-92ee-75cd86b75bc1_5gyrq6psz227t!App for the Windows. Launch contract was blocked with error 0x80073CFC because its package is in state: Modified‘. We checked through on your sites and it is mentioned that Enterprise Sideloading key is mandatory for the app to work if the machine is not connected to the domain.
If we publish the app on Windows Store using ‘Targeted App Distribution’ method, do we still need to worry about the Enterprise Sideloading key or will the key be available when we will create a developer account on the Windows Center? Let us know.
Let us know if we are missing anything. Also, it will be helpful if you suggest any appropriate way as we need the Windows app to work without being connected to the domain.
Thanks
You could sideload the app if you have a developer license registered on the target machine. You can get a developer license via Visual Studio or with this powershell command:
Get-WindowsDeveloperLicense
However the developer license needs to be renewed every month.
See my answer here how to sideload an app:
sideload windows 8 apps to multiple devices?
Using Visual Studio 2013 Ultimate update 4, I have developed a universal app for the store and the phone under Windows 8.1. The app is implemented upon the Prism for Windows Runtime.
The app is at its final testing stage. I have no problem to run/test it with the corresponding emulators and devices (Surface Pro and Lumia 1020) until few days ago. Although the app can still run/test with the emulators (The store app can be still packaged and deployed to Surface Pro for testing). But I will receive following error message when running with device (Lumia 1020) under Visual Studio 2013:
Unable to activate Windows Store app …. The xxx.exe process started, but the activation request failed with error ‘The app didn’t start’.
I have tried all followings in number of times, still received the same error message (there is no app.config file used in app (at least not being seen in the solution pane and windows explorer):
Roll back to the change set where I have successful made the build and deployed to Phone.
Run repair on Visual Studio
The problem has been fixed.
I have used MS Ocr Lib. for Phone once which only works for ARM. After using NuGet to remove Ocr lib., OcrResource folder still remains in the phone project.
To fix the problem, one must either deletes OcrResource folder if the target platform is for Any CPU, or keep OcrResource folder and set the target platform as ARM.
We have few windows services developed using .Net framework 1.1(VS2003).For each windows service an msi installer(set up project) is created to make installation easier.These installers are able to install windows services successfully in windows XP.But these installers unable to install windows service in WIN7 though I have admin privileges on the machine in which I am trying install them.While I am trying to install the windows service in win7, Through msi installer,installation is progressing till 90%.After that it is neither completing nor throwing an error.I am unable to understand what the problem is.
I tried following ways.
1.Opened cmd window in admin mode and tried to execute the msi with the command msiexec -i --Din't work
2.Right clicked on the actual exe(windows service exe) file and tried to run it in admin mode.--Din't work
3.Changed the UAC to never notify, restarted the machine and then tried to install--Din't work
4.Right clicked on both exe and msi and open their properties and changed the compatibility to lower version of windows and tried to install--Din't work
One thing I have noticed is that for all the custom actions of our windows service installer, primary output of our main project(exe) was given as input.I build the msi installer by removing all the custom actions.Then i tried to install it in win7.Then it was installed.But during the installation system not prompted for account details (which is the actual case while installing windows service) and also the service was not appeared in services manager window.
I spent somuch time to identify the cause and resolution.But I dint find any posts on this issue.I suspect that the problem is with custom actions.But not sure.If the problem is with custom actions please let me know how to overcome it.
Please provide a resolution for this issue or share me if there are any links which talks about this.
FWIW, .NET 1.1 isn't supported on Win7. Also I'm guessing you are using InstallUtil custom actions to drive the setup of your .NET Windows Service. These are very fragile and you can eliminate all those brittle points by refactoring and using the ServiceInstall ServiceControl tables in MSI.