Two weeks ago I was able to run and analyse .net projects on windows 10 but after some times, it stopped. I am getting this app can't run on your PC , To find the version for your PC, Check with the software publisher.
I was following this url Scanning using Ms Build
I have also changed my local security option, the option of allow UIAccess applications to prompt for elevation without using the secure desktop to Enabled.
I am using windows 10.0.16299 x64 and there is no recent updates done on the computer.
I am running the command from sonar-scanner-msbuild-4.0.2.892\SonarQube.Scanner.MSBuild.exe and I have sonarqube-7 installed and running.
What Am I missing, I am not sure what caused the execution to stop and I checked there is no antivirus or firewall blocking and there is no error .
Related
I have created a WPF desktop application using the community edition of Visual Studio 2017.
The problem that I am facing is that my application does not run on some PCs where I try to install my application whereas it runs fine on others. On the OCs where it does not work, when I execute my application no errors are thrown but in the task manager the status of my process changes to suspended and then the process is removed from the set of running processes.
I am able to debug and run application on my PC (Win 10 64 bit OS), and on couple of other PCs that have Windows 8 64 bit OS, but the ones on which the application fails to run are Windows 10 PCs, but I am not sure if Win 10 is the problem since the application is running on my PC.
When creating the installer for my application, I have the following options selected:
.Net framework 4.6.1(x86 and x64) as a pre-requisite.
Download prerequisites from the same location as my application.
I need help in debugging what is cause for this problem, since at this point I do not know what is stopping my application from running. How can I debug what is going wrong on these deployment PCs?
I have tried installing on different PCs, but could not identify the reason why it is working on some whereas not on others.
I thought maybe the "Microsoft Visual C++ Redistributable 2017" is a requirement so I downloaded and installed on the client machine but this too did not help.
I also disabled the anti-virus software, but this too did not help.
Helo,
I am developing UWP Application.
Trying to install build (by Side loading) in various systems.
All systems are windows 10 only, but having different processors. Some systems supporting with Debug mode generated builds and some systems supporting with Release mode generated builds. I am unable to track this issue. Why can't single mode build (whether it may be Debug or Release mode) supporting for all windows 10 systems. Can any one tell me what are the client system requirements for installing and working with UWP applicatiton.
Below is my client machine system specifications
And I have generated build in Release mode by selecting both 64 and 32 bit, after side loading I got files like below
Application installing successfully, but when i am trying to open it's getting crash.
I have observed one change In Client Machine.
Marked one getting extra in Packages folder.
I have verified windows log, it's showing below error.
Activation of app fb23829-a660-4c2e-88df-bc3c735654f7_a2ct2483cqfyg!App failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.
After so many trails I came to know that if target machine having i3 processor then at the time of generating the build we should select only one type i.e., either it may be 32 bit or 64 bit. if we select both then application will Crash.
I recently had to uninstall/re-install .NET Framework 3.5 on my new Windows 10 work machine to troubleshoot another issue. I have to install it via SCCM due to Group Policy blocking Windows Updates (so I can't just install via Control Panel > Turn Features On/Off).
When attempting to re-install through SCCM the install just spins in the Installing state indefinitely until it times out.
Steps taken:
Uninstalled the .NET 3.5 Framework via Turn Windows Features On and Off in Control Panel and restarted machine.
Went to SCCM and attempted to install software, and it hung indefinitely.
After 2 hours I restarted machine to check if I just wasn't alerted it was finished for some reason
Install did not finish, Failed status shows with the error code for timeout in SCCM.
Other Info:
I verified no errors were generated in the SCCM log files or Event Viewer.
I can't install via Control Panel MS Update download as mentioned above due to Group Policy, I can't do an Offline install b/c these laptops don't have a disk drive (for whatever reason that was decided to be ok), and I can't do a system restore to before I removed it due to drive encryption software.
No admin accounts or similar can get different results, and I've verified it is not the SCCM install itself after getting it to install on another machine just fine.
I've ran both the .NET Framework Repair tools and Clean-up tools and I still get the issue.
Any ideas on what I can try?
If anyone encounters a situation similar, I was able to fix it by extracting the microsoft-windows-netfx3-ondemand-package.cab file from the .iso of Windows 10.
Using that file you can run the following script in an elevated (administrator) powershell and it will install the files offline for you.
Dism /online /enable-feature /featurename:NetFX3 /All /Source:<path to file>
I have created a windows application using c# VS express 2012. The app works great in the VS environment. I have published the application using VS(ClickOnce) to the Desktop as an offline application, which does not check for updates. The app is not signed and security is disabled. The application seems to install fine when I run the setup.exe file. However, when I try to run the program from the start menu nothing happens. In the task manager, a process for the application appears for a few seconds then just goes away. The app window doesn't show and there aren't any indications of an error. If I navigate directly to the .exe of the app (%userprofile%\appdata\local\apps\2.0\%random id%......) and run it that way, it starts up and appears to function as designed. I've done some research and found that certain drivers and software (if installed) will cause this behavior (i.e. Kensington Mouse driver and Provencia software(?)). I've checked and I do not have either of these installed. Any help with this will be much appreciated.
Thanks in advance.
I am working on a project where several software and drivers are installed on a windows 7 PC. This shall work without user inputs.
Now there is the question: How can I determine in this program if a reboot is required to finish an installation (can be driver or software).
We are working on Windows 7 embedded and there is no taskbar enabled or any tooltips or something like this visible. Software is installed in silent mode.
Use the following registry key:
HKLM\System\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations
Source: How to find out if an MSI I just installed requested a windows reboot?
As discovered by the asker of this question HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\RebootPending shows when a reboot is pending on the machine as long as the OS is Vista or newer.
After a long research I found a way how to query pending restarts with a native Windows DLL directly in a .NET application.
The main problem is that there can be many reasons why Windows has to restart. In addition, the Windows version sometimes also plays a role.
During the research I came across an article describing various scripts in the Windows Update environment, such as determining whether the automatic updates service is enabled or a computer needs to be rebooted. There you will find a reference to the Microsoft.Update.SystemInfo Object, which finally led to ISystemInformation interface having the method ISystemInformation::get_RebootRequired (Gets a Boolean value that indicates whether a system restart is required to complete the installation or uninstallation of one or more updates.).
For more details about the journey, see my blog post Determine programmatically pending reboot status for a Windows machine in C# and PowerShell
The "PendingReboot" module incorporates all the mentioned tests (+ CCM WMI probe) into a single convenient cmdlet to reliably detect pending reboot:
# Install
Install-Module -Name PendingReboot
# Run
Test-PendingReboot -Detailed