I am installing Cognos Analytics server by right clicking on the setup file and running as administrator. But I can't continue because it does not show me the license agreement and the option to accept it.
I have Windows 10 and have administrative rights on the user account. Also, the installation file is on C:/Temp/. What am I missing here?
I can only guess as to why the EULA isn't showing up. Perhaps the download is corrupted or you have some graphics issue on the system on which you're installing it. Can you run the installer on another computer simply to see if the EULA prompt shows up correctly?
To circumvent the issue entirely, assuming the download is not corrupted, you could use a response file installation. This would allow you to install the product "headless," which would avoid the need to click through the graphical installer.
The silent installation instructions direct you to provide a response file when running the installation, a template for which can be found here.
Related
I was getting this error when trying to install Atom using the installer.
I tried to run as Administrator but ever having the same error.
So I opened the Setup Log and found this line in many places of the log:
Failed to load local releases, starting from scratch: System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\david\AppData\Local\slack\packages\RELEASES'.
To resolve this problem, I simply tried to change the AppData folder properties, unchecking the Attribute "Read-Only" and applying to subfolders.
After that, I could install the application and everything is working well.
I don't know whether what I did was the best solution, but it fixed my problem :)
Hope this help someone
If you have anti-virus installed on your system. Please disable it and try it once. Hope this will work for you because this worked for me like a charm.
One more thing you can check that your windows update service is also running. You check it out in Task Manager ->
So do this thing and check it out.
This is a permission related issue. Could be you don't have permission to write, in that case run as Administrator.
Right Click on the installer and select Run As Administrator.
If you still have the issue, disable your antivirus, defender or whatever you have to protect your PC from threats. Once Installed Enable it BACK
if you have Dropbox opened, close it.
You can try this:
open control panel
Windows firewall
click allow an app or feature through windows firewall
In that at right bottom click allow another app
Browse the downloaded atom.exe file and click open and click ok
first uninstall or disable the antivirus. In my case Guardian net secure was handling all the things of windows firewall. so i was not able to allow the app through windows firewall. therefore, it is necessary to uninstall these. then restart your laptop.
after restarting open control panel. go to windows firewall. on left top you will see
allow an app or feature through windows firewall . click on it. dialog box appears. click on change settings. at bottom click allow another app. then browse the downloaded file atom.exe. then install it
What worked for me was closing Slack and terminating any of it's processes in Task Manager.
This was what worked for me (Windows 11):
Go to properties>compatability on the installation file. Run the troubleshooter for compatibility, and it shoul provide a solution, wait, and if it works, select that it did so, and you’re all done.
To resolve this problem, I simply tried to change the AppData folder properties, unchecking the Attribute "Read-Only" and applying to subfolders.
After that, I could install the application and everything is working well.
This worked for me on Windows 11 home version.
Hope this helps
I managed to install by finding an older version.
I'm trying to install svnX 1.3.4dmg for iMac. It says “svnX” can’t be opened because it is from an unidentified developer. how can I do that. please help me with this.
These instructions are for OSX Yosemite, and may not apply to all versions of OSX. Let me know if you need directions for another version. Also, a warning to anyone attempting to do this with potentially unsafe software, please be sure the program you are installing is legitimate and safe prior to running the installer. See the article linked below for more information about this topic.
To override your security settings and open the app anyway:
1. In the Finder, locate the app you want to open.
2. Don’t use Launchpad to do this. Launchpad doesn’t allow you to access the shortcut menu.
3. Press the Control key, then click the app icon, then choose Open from the shortcut menu.
4. Click Open.
The app should then be saved as an exception to your security settings, and you can open it in the future by double-clicking it just as you can any registered app.
Here is the Apple Support article I took this information from: https://support.apple.com/kb/PH18657?locale=en_US
If anyone is curious, these are the keywords I used to search for solution (Google):
Mac OSX install program bypass unidentified publisher
I am trying to install Remote Tools on a Surface RT running Windows 8.1 preview. I downloaded update 2 of remote tools from Microsoft's site and when I try to run it I get the error:
Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
This is confusing because I downloaded the file directly from MS website and when I look at the .exe properties it says digital signatures by Microsoft Corporation.
Any insight would be greatly appreciated.
Thanks!
Update: It seems like my Microsoft Root Authority certificate is "not valid for the selected purposes" I've tried exporting a "good" certificate from another machine and importing it into the Surface machine but it still gives the same issue.
This is because your downloading the 2012 tools. You can download the 2013 preview tools here at the following link! (Be sure to choose ARM)
http://www.microsoft.com/en-us/download/details.aspx?id=40781
Would have been nice if Microsoft had given us a heads up.
Also, when I go to the 2013 download on my Surface RT running 8.1 preview, and I click on Download, no matter which option I pick (x86, x64, or ARM) it downloads the x86 version, which obviously won't work. I had to download it on a PC and copy it over using a USB drive.
This problem exists on the released version of 8.1 too.
If you previously had the vs2012 tools installed, they appear to be uninstalled during the upgrade.
Attempting to reinstall gives the above error.
That means, it's now impossible to connect to the 8.1 Surface RT from VS2012 Pro to debug an 8.0 app running on 8.1. Instead, you need to connect with the VS2013 tools and remote debugger.
For anyone who is just trying to test their App updates a surface device running Windows 8.1 RTM, I have at least found a workaround.
You can manually deploy your package to your device by coping the package content to a USB memory stick and running a already defined powershell deployment script.
Basically you need to run the normal package creation process you would do to deploy to the app store to create a package, then copy the contents of the package folder (Not the compress package itself) to your USB stick. There should be a file named Add-AppDevPackage.ps1 in this folder.
Open your USB device from your Surface RT system, right click the Add-AppDevPackage.ps1 file and select "Run with powershell". You will receive several confirmation prompts at the command line and a popup window prompting you to run with admin privileges.
This is by no means a convenient or speedy process but it worked for my purposes.
This link has more detailed information on manually deploying your app package.
I have a network with one server that is connected to the internet and some clients that are not.
I want to download and install Microsoft products on my server first and let the client computers download the installer later from the server.
The questions are
where does the WPI save the downloaded files?
is it possible to run WPI and force it to install the Microsoft products from the already downloaded files rather than downloading again from Microsoft's server.
Note: Assume there is no license issue, hopely :-)
It will be cached under %LocalAppData%\Microsoft\Web Platform Installer\installers if you are on Vista or above, or in the equivalent location on XP (there is no %LocalAppData% environment variable in XP).
If the products are downloaded, they will be installed again from the cached location, unless they were updated, which would change their hash and force Web PI to download them again. Moreover, you can copy the cache folder from one computer to another to the same location and Web PI will pick it up automatically and install products from cached installers.
Microsoft has released a tool called Web Platform Installer v4 Command Line which has a switch to prepare an offline installation. Quote from the page above:
Creates an offline cached copy of a specified set of products and
applications so you can install while offline
Example:
Ex: >WebPICMD.exe /Offline /Products:WebMatrix,SQLExpress /Path:c:\OfflineCache
The above will create an offline cache at c:\offlineCache that contains WebMatrix and all it's possible dependencies!
Update 2017
The link above is no longer valid (404). The page i found is
Web Platform Installer v5 Command Line (WebPICMD.exe) - RTW release
WebPI Command line
The Web Platform Installer v5 (WebPI) command line tool is now
available as part of the WebPI MSI! We've added a bunch of new
features and fix several issues, and now it's ready for it's full
release
On the page are two links
WebPI v5 x86.msi
WebPI v4 x64.msi
Microsoft has released a beta tool that will do this.
In windows 8 I found it here
%AppData%\Local\Microsoft\Web Platform Installer\installers
I have a setup which has been created using InstallScript MSI project type. This problem is encountered by our client and he wants a quick solution.
Let's assume I have initiated the installation from a path like
C:\Setup_V_1.0.0931.1
Inside this folder I have Setup.exe through which I will install the product. After installation or after some days pass I will change the path to:
C:\New\Setup_V_1.0.0931.1
and this time I want to modify the setup. Actually we are supporting 3 features: Server, Client and Service.
This time I want only Client and not Server. So I will click on the Setup.exe or click on Uninstallation Icon in the Startup Menu which will lead to Maintenance Mode there you have an option to Modify, Repair or Remove. I choose Modify and select the feature, but as the installation progresses, this error message will pop up:
Setup could not find a file on the specified path or Disk. Please check
that the proper disk is inserted or specify a new path. Unable to
locate file c:\New\Setup_V_1.0.0931.1\setup.msi
Then, another popup will be shown saying:
Error: 1706. No Valid Source could be found for product. The Windows
Installer cannot continue.
The next error message is:
Error: 1603. Fatal error during installation. Consult Windows Installer
Help (Msi.chm) or MSDN for more information.
But if I change the path to its original location, it works fine.
How can I solve this?
I event checked in this registry path:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\{Product-Key}
This key contains a lot of information inside InstallProperties. There is a key called InstallSource and its value is C:\Setup_V_1.0.3909.1\. Even after changing this value installshiled is still showing errors.
I found the same registry information for Uninstallation Information:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{Product-Key}
In your properties change ReinstallMode (or maybe Reinstall I forget which) from omus to vomus
the v means cache your install, so it will put your .msi file in c:\windows\installer so it can be used later.
When installing a MSI, Windows Installer saves the original MSI path in registry (the InstallSource entry you mentioned). When running the MSI in maintenance mode, Windows Installer will use this path to find the installation data (CAB files).
When you move the MSI, the path stored in registry is no longer valid, so Windows Installer cannot find the installation data.
A possible solution is to use "Add or Remove Programs" or "Programs and Features" in Control Panel to modify the installation. This way the cached MSI is used.