My install-shield 2010 is not opening only the splash screen is opened , it was working fine earlier.I have uninstalled it and deleted all the files in app-data,program-files and the registry,im confused if some other app might be blocking this EXE to run (Because it was working properly earlier).
it happen to me from time to time, the problems is usually because the auto reactivation of my licence failed.
their's a tools for that called TSConfig.exe in C:\Program Files (x86)\InstallShield\2015\System.
If it's not that, you can still check in the InstallShield.log in the same directory, it might give you more clues.
EDIT :
I Just found the email that the Flexera support send me back in the day
Close InstallShield
Locate tsconfig.exe on the machine (the default location is:
C:\Program Files\InstallShield\2011\System)
From a command prompt, run the following command: tsconfig.exe /return
Launch InstallShield
If prompted proceed with activation using serial
number
Related
I created a simple installer in NSIS. During installation, the maxscript files are copied into the corresponding folders of 3ds max and keys are created in the registry for uninstall. The installer works fine in Windows 7, but when i try to run it in Windows 10, the installer is blocked and a warning message appears about the trojan (see image) > Win32/Sprisky.U!cl
On my computer this is not a problem for me, I know that there are no viruses and trojans and just continue the installation, canceling any Windows Defender actions. But for other users this is a problem and they are afraid to continue the installation. Why does Windows Defender consider that the NSIS installer is a trojan or a virus ?? How can you get around this and what should be written in the installer script code so that WIndows Defender shut up?
Thanks for any help!
There are no code changes you can make to remove the warnings. NSIS produces an application that extracts compressed files and executes interpreted code on the fly and this sometimes triggers false positives in antivirus software.
Your only option is to report the false positive to the antivirus vendor.
i'm trying to install visual studio 2013 into my windows 7 32 bit system. I've encountered the below error during installation
"This update package could not be opened. Verify that the update package exists and that you can
access it, or contact the application vendor to verify that this is a valid Windows Installer
update package."
Help me out
it is windows so i am guessing: the installer package is corrupt or follow this link: http://kb.eset.de/esetkb/index?page=content&id=SOLN561
try to make some md5 sums of your files and google for them.
Normally this issue will occur if you are having permission issue or compatibility issue.
For permission issue:
Right click on the executable and run it with run as administrator option and check.
If above is not working then check for the compatibility issue by following the steps below:
To Run the installation program in compatibility mode:
1. Right-click the installation file's icon.
2. Click Properties > Compatibility .
3. Select the compatibility mode for Windows XP.
4. Click OK .
5. Run the installation program.
After it's installed, run the program in Windows XP compatibility mode by doing the same with the installed program.
If you have an older application for Windows XP or Vista that doesn't run in Windows 7, you may be able to get it working properly by running the program in compatibility mode.
1. To begin, find the application or shortcut that is causing the problem, then right click on it and select Properties.
2. Then, select Compatibility from the tabbed menu at the top of the properties page:
3. Now, check the "Run this program in compatibility mode for..." box and select the OS you wish to emulate. For most applications, it will be Windows XP SP2. Once you are done, click OK.
4. When you next launch the application it should run under compatibility mode using the OS you selected. If it still fails to run correctly, try another OS selection in step 3 and try again.
Visual Studio 2012, VS 2012 Command Prompt, VS 2010 Command Prompt, and a C++ console application compiled in 64-bit with VS 2012 are all reading an out of date instance of various registry keys. Each application (i.e. VS 2012, the command prompts, and the compiled app) all seem to have their own version of this out of date registry. Below are the symptoms I'm seeing and my various attempts to fix it.
I've both added new registry entries and updated the data in existing ones and all appear updated in HKLM\Software\ viewing them with RegEdit and using 'reg query ' in a normal console window.
Using the VS Command Prompt I perform the same query and get registry entries prior to my updates. If I open up a VS 2012 command prompt and perform edits using command line arguments the registry for that VS 2012 command prompt is now different than the registry read by the VS 2010 command prompt. It is also different from the VS 2012 IDE and the application built from VS 2012. They seem to have their own instances of whatever version of the registry they are reading from.
Finally, I opened up the Visual Studio 2012 command prompt and typed Regedit. It opened up RegEdit and it was viewing the old registry! All of the stale values within HKLM\Software\ were present - a seemingly completely separate version of the registry. Where is it getting this from?
My environment: Windows 7 Enterprise, VS 2012 Ultimate, console application built in 64-bit.
It should be noted that I have not made any major environment changes that I recollect and this is a new issue on my previously working development system. My colleagues have the same/similar environment and hardware setups with the same code base and have never encountered or seen this issue.
Things I've tried.
The almighty reboot
Uninstalling / Re-installing VS Studio 2012 as well as wiping out my code base, pulling it fresh and rebuilding (brute force I know...).
Checking the Registry for Wow6432Node keys to see if the reads/writes are getting redirected (I do not have a HKLM\Software\Wow6432Node and no other instances of that key have the old stale data or much else for that matter)
Searching the entire registry for the stale keys/values/data I'm seeing (not found anywhere)
Turning off virtualization using 'reg FLAGS hklm\software\ SET DONT_VIRTUALIZE DONT_SILENT_FAIL RECURSE_FLAG' as well as variations of this with one flag at a time.
Writing and debugging a unit test to try and determine anything.
VS 2012 safe mode
VS 2012 logging to see if the log file could shed any light on the problem.
Cursing (quietly because I'm at work)
Bribes (my workstation has yet to respond to these attempts)
Any help would be greatly appreciated. I'm close performing a clean Windows installation on my workstation but would rather save myself the time and trouble of setting everything up again :)
I am attempting to launch the windows phone 8 SDK emulator on my Mac so that i can do simple web testing of mobile websites i build.
I have followed several guides and they all say the same thing.
Such as:
6. Once the content (list of files and folders) is displayed, find the VMware virtual machine configuration file – the file with the .vmx extension.
hypervisor.cpuid.v0 = “FALSE”
And this guide proved to be quite useful to get it setup:
http://developer.nokia.com/Community/Wiki/Windows_Phone_8_SDK_on_a_Virtual_Machine_with_Working_Emulator
I was able to get Hyper-V support enabled and I have even managed to open the Windows Phone 8 Emulator directly from the Hyper-V Manager. But in this state it is missing the chroming, the buttons, and when the mouse goes across the screen it disappears. The solution to this is said to be launching the emulator directly from Visual Studio.
My problem is when ever i try to launch the emulator from Visual Studio it creates a new image and then goes into a boot look where it keeps crashing and restarting over and over again.
When viewing the Hyper-V event logs i see this error:
'WP8SDK720P' has encountered a fatal error. The guest operating system reported that it failed with the following error codes: ErrorCode0: 0xC000021A, ErrorCode1: 0x88EB9150, ErrorCode2: 0x0, ErrorCode3: 0xC0000022, ErrorCode4: 0xD203BC. If the problem persists, contact Product Support for the guest operating system. (Virtual machine ID 50607D9A-6E23-4369-9D89-2730614219BA)
How can i get past this error?
In the end I found a solution, I managed to launch the original Windows Phone VM image directly from the commandline with this command:
"C:\Program Files (x86)\Microsoft XDE\8.0\XDE.exe" /vhd "C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v8.0\Emulation\Images\Flash.vhd" /name WP8SDK720P
I created a new text file with notepad and put this command in it and saved the file on my desktop as a .bat file. This way i can just double click the shortcut and launch the sim.
Hopefully this helps someone else out there. In this way, you don't even need to start visual studio to run the emulator, it makes it much simpler if all you are using the emulator for is testing web-apps.
N.B. if you press FN+DOWN-ARROW you can enable the keyboard to work in the sim.
Follow these steps and see if it might help you to fix the problem.
Step 1: Shut down the Guest operating system (Windows 8 in this case).
Step 2: Open the settings for the VM and select Processors. Look at the left pane and see if you have CHECKED the option "Virtualize Intel VT-x/EPT or AMD-V/RVI" under the Virtualization engine section.
Step 3: Open the configuration file (Windows 8 x64.vmx) for the VM and check if you had added the following line of command (hypervisor.cpuid.v0 = "FALSE") to it as shown in the screen shot. You will generally find the file at the location where the virtual hard disk is placed.
If every thing is right, check to see if you had installed Visual Studio 2012 Update 3 (if you are using Visual Studio 2012 as your IDE).
Hope this helps to fix the issue. If you need more information on how to create a VM for developing windows phone 8 apps, there is a great article on nokia developer forum. You can find it here
Happy Coding!!
I am getting the following error when starting Visual Studio 2012 as unprivileged user:
An error has occurred while trying to access the log file. Logging may not function properly.
A casual web search showed that the issue used to exist with VMware 6 beta, back in 2006. I also found one other user who experiences the same in a more recent VS version (2008) and it started only recently.
The title of the message box indicates that this comes from VMware. I have VMware 9 Workstation installed. The problem could be related to system updates or the update 2012.2 CTP and hasn't gone with the final 2012.2 update package.
The question:
How can I get rid of the error without actually disabling the VMDebugger add-in?
Temporary workaround:
There is a workaround, disabling VMDebugger in the "Add-in Manager". However, it even seems that unprivileged users are unable to successfully disable it. I had to start VS as admin (I am using SuRun for the purpose) to disable it and the error not reappearing upon next start of the IDE.
I had the exact same problem, this is how I solved it.
I monitored devenv.exe using procmon to find the log path, on my computer it was: %TEMP%\vmware-username
I checked the permissions on the log directory, and discovered that my user had no access - neither read nor write! I gave myself full access and deleted the old log files. That solved it for me.
I think this happened because UAC was disabled when I installed VS and VMware.
In Visual Studio, go to the menubar to VMWARE / About VMWare Virtual Debugger; the Debugger log file will be listed there, e.g. C:\Users\Phil\AppData\Local\Temp\vmware-Phil\vmware-vsid-1.log
Give your user full access to that file.
(This solution was for Visual Studio 2013, VMware Workstation 11.1.2, Windows 8.1.)
The fastest and easiest way to solve is...
1. Locate the folder %temp%\vmware-{username}
2. Delete this folder. The folder will be created by opening the Visual Studio.
Note: You need to open the Visual Studio without admin rights to resolve the issue!
Background: Mostly this happens if you use the VMware debugger plugin the first time under admin rights (because your app may need this right to run properly). This creates the folder under admin rights with the admin permissions. Everytime you open the Visual Studio with admin rights, you have no problems.
Examples
Windows: C:\Documents and Settings\<username>\Local Settings\Temp\vmware-<username>-<PID>.log
Linux: /tmp/vmware-<username>/ui-<PID>.log
This post helped me
The fastest and easiest way to solve is...
1. Locate the folder %temp%\vmware-{username}
Go in windows+R %temp% , delete all , ready !