We have an app which uses squirrel.windows for installation and updating. When executing Setup.exe it can't extract the installer and we get the following error message:
It tries to install to the ..user//AppData.. directory.
Setup.exe works perfectly for Windows7 and it used to work for Windows10 (we don't know exactly when it stopped working).
We tried to run Setup.exe as administrator and in compatibility mode, however it did not help. But running Setup.exe as Domain-administrator works, so we expect that something changed with the user-rights in Windows 10. We also updated squirrel.windows to the latest version (1.9) and added SQUIRREL_TEMP to the environment variables, but nothing helped.
Any suggestions what could be wrong?
I don't know why, however, upgrading Squirrel.Windows to version 1.9.0 fixed the issue.
This is pretty late to post, But if someone stumbles here please read this,
Workaround -
Please try disabling Antivirus software if any. In my case, user had Kaspersky AV, so disabled it for an hour and tried installation it worked.
Solution -
The robust solution would be digitally signing setup.exe that is generated by Squirrel (using releasify). Please refer this for details
Related
I have Imagemagick running on a remote server and have had it running on a local server successfully for many years, but recently I have had need to reinstall on a new machine and can't for the life of me figure out what i'm doing wrong, It's probably really simple and I'm hoping someone can point me in the right direction.
Scenario
WIN 10 running iis as localhost
Successfully installed Imagemagick 32 and 64 bit so they run on the local machine, however when try to access the localhost web page requiring Imagemagic I'm receiving the following message
Microsoft VBScript runtime error '800a01ad'
ActiveX component can't create object: 'ImageMagickObject.MagickImage.1'
my app pool is current set to allow 32bt application and as far as I am aware all permissions are correct, although I do believe this may be the issue somewhere.
Can anyone help to shed some light on this issue.
Thanks :-)
Resolved.. It turns out the latest version of Imagemagick 7.1.x does not ship with ImagemagickObject.dll, fortunately, I had a saved download .exe for an earlier version 7.0.8 which still had the .dll, once install I could copy imageMagickObject.dll to the system32 folder, after that everything worked as expected. Not sure what would replace this in my code if I have to ever user a newer version, if someone knows please add to the post.
We are using node to build the LESS files in our .NET application.
To do so, we have prepared some stuff to support that easier for all the developers. In the end we have a node version in the source control.
Everything works fine for everyone except one developer that has joined our team in the last days.
Whenever he tries to run the stuff, the CSS files are just empty.
To find the reason we have tried to skip all the stuff around and call node with the less package directly from console. This is working as expected on my PC but there is no output at the affected developers PC.
Also when we are using a path to not existing package there is no output.
On my PC there is an error logged into the console, the affected developer does not get any output.
The only parameters that seems to work are "-h" and "-v"...
As we could not find any usefull hints in the internet, maybe anyone having an idea what can be reason?
Windows-configurations, ....
Finaly we could solve the problem:
Don't ask why but uninstalling Visual Studio 2019, installing VS 2017 and installing 2019 again solved the issue somehow... everthing works as expected.
Reinstalling VS 2019 alone did not solve the problem before.
Maybe a hint in case someone else comes to this question with the same issue:
The reason for going to VS 2017 where different issues with ReSharper as well. Mainly performance issues of VS when ReSharper was active, but some functional issues too. This issues where gone as well after that.
It seems there was something broken with the VS2019 installation that was not repaired by uninstalling and reinstalling VS2019 but by VS2017...
I am trying to install Oracle 12c client on my development box running Windows 10 and it doesn't even start.
I downloaded the files from Oracle download web site, ran setup.exe and it flashes briefly and nothing happens. I made sure latest JRE and JDK are installed.
I have spent most of the day googling but most deal with errors that occur during installation whereas I can't even start the installation! No errors, no messages. Checked GAC on off chance DLLs might be there but they are not.
I have used the same set of files on other machines and servers (Windows 2008r2 and 2012r2) without any issues but can seem to be able to troubleshoot this one. Any ideas to put me on the right path is appreciated.
After spending a couple of days trying to figure out the issue, uninstalling/reinstalling JRE and JDK and all that, the issue turned out to be the hard drive size. Apparently max dive size where you install the client is 2TB and mine was 3TB. I had to shrink the drive and it worked after that. Hopefully it saves someone some pain.
A couple of links for more info.
Installing on large disk
Oracle Universal Installer
I recently migrated windows 8.1. But unable to open vs2013/vs2012 new Project template.
IT was working fine in windows 8.
ERROR: Failed to create imageSource from the text '..\Images\Medium.png'
Tried all options but did not succeed.
Please HELP
This is because you migrated from windows 8 to windows 8.1
First Go to Control Panel --> Check Updates for Windows 8.1
Install All Important Updates
Restart Your Pc
All things will properly work..
I tried almost every solution I found.
I would like to share, what I have tried and did not work and what did work and solved the problem.
Here are the "solutions" which did not work for me but claimed that they worked for some people.
1) Removing FastPictureViewer Codec Pack (which was already not installed)
2) Having a modify permission to everyone for
c:\windows\microsoft.net\framework\v2.0.50727\config\machine.config
and
c:\windows\microsoft.net\framework\v4.0.30319\config\machine.config
3) Using Procmon to see broken registries
4) Uninstalling/reinstalling VS13 and all shared packages
5) Renaming the machine.config.default to machine.config
6) Running Visual Studio as an administrator
And this what it solved it:
Simply installed all the updates for windows 8.1 (not only the important ones, also optional updates as well) and restart. It sounds crazy after spending hours and hours but that solved my problem.
Good luck!
I tried all the steps mentioned above and it did not work. Even I was not able to uninstall VS.
I reapaired .NET framework through Contrl Panel->Programs and Features-> Microsoft .Net Framework-> right click Chane/Uninstall Repair .Net Framework.
This solved the problem.
I got same error after Oracle Data Provider for VS 2013 installation. I installed all Windows 8.1 Important Updates but it didn't work. I read somewhere that it can be happened because of lastly installed VS Add-On etc. then uninstalled Oracle Data Provider for VS 2013 and problem solved.
I am using Visual Studio 2012. This problem occurred to me after I upgraded from Windows 8 to Windows 8.1, so it is definitely related to the OS upgrade.
As some answers say, installing updates for Windows 8.1 will resolve the issue. But you don't need to install everything. I installed only the .NET related updates. Specifically, I installed "Microsoft .NET Framework 4.5.2 for Windows 8.1" (KB2934520), and a few others "Security and Quality Rollup" updates as well.
After a reboot, the "Loading Components" dialog shows up briefly upon launching Visual Studio, indicating that the cache of some components are invalidated and they are compiled again. After that, the "Add Reference" dialog works again.
I just upgraded to windows 8 from windows 7. Visual studio 2010 broke down completely. Oh well. I removed vs2012 and installed visual studio 2012, where the pain starts. I have been reinstalling vs 2012 a couple of times. However, the symptom remains the same.
When I try to create a new project (FILE -> New -> Project or ctrl + N).
It pops up with an error message dialogbox saying
"Failed to create a ImageSource from the text '..\Images\Medium.png'.
" I am like ##*%&^#*###(. So can anyone please tell me what is going on with my Visual Studio2012?
By the way, I can open and run the existing vs2010 projects with no problems.
I definitely neither want to do a fresh install on windows 8 nor rolling back to my windows 7.
Cheers,
To resolve that problem, I've change the permission of "modify" for "everybody" on the files
c:\windows\microsoft.net\framework\v2.0.50727\config\machine.config
and
c:\windows\microsoft.net\framework\v4.0.30319\config\machine.config
Don't know if it's the best way to do it, but at least it works.
Do you have any codec packs installed on your system? I had a WIC codec pack for viewing RAW files in Explorer, and it resulted in the same issue you are describing. Uninstalling the codecs fixed Visual Studio for me.
I was having various issues, including the above.
To resolve the problem on Windows 8 for VS 2012, setting it to run as administrator fixed the problem for me.
Launch icon properties->Advanced Properties->Run as administrator
I hope this helps.
Cheers,
Sean
The trace of this issue leads to Windows Imaging Component (one solution proposed was to remove FastPictureViewer, which codec affects WIC, but it was not my case). I used procmon to log all file and registry calls and found that VS2012 stumbles at the following key:
HKLM\SOFTWARE\Classes\.png - REG_SZ Content Type
I was suprized to see that Content Type for .png was set application (for .jpg it was application as well). After correcting it to image/png, not only VS2012 started successfully, but VS2010 as well, that was showing "Provide value on System.Windows.Baml2006.TypeConverterMarkupExtension threw an exception" on Win8 and caused me to try VS2012.
I had the same problem with Visual Studio 13.
uninstalling/reinstalling VS13 and all shared packages did not solved the problem.
Finally I tried to run it as administrator, as explained above and it worked.
Just happened to me. As Eric Aubry said check the machine.config file. In my case it wasn't permission error but the fact that the file was destroyed internally. By renaming the machine.config.default everything was fixed.
For me, this happened when I installed mysql on my machine, and it added an extra connection string to my machine config. However, since I was using a separate file for configSource, it resulted my machine config to become corrupted.
Moving the new config key to my config source from the 32bit machine config solved the issue.
As I mentioned in that question ,
I tried almost every solution I found.
I would like to share, what I have tried and did not work and what did work and solved the problem.
Here are the "solutions" which did not work for me but claimed that they worked for some people.
1) Removing FastPictureViewer Codec Pack (which was already not installed)
2) Having a modify permission to everyone for
c:\windows\microsoft.net\framework\v2.0.50727\config\machine.config
and
c:\windows\microsoft.net\framework\v4.0.30319\config\machine.config
3) Using Procmon to see broken registries
4) Uninstalling/reinstalling VS13 and all shared packages
5) Renaming the machine.config.default to machine.config
6) Running Visual Studio as an administrator
And this what it solved it:
Simply installed all the updates for windows 8.1 (not only the important ones, also optional updates as well) and restart. It sounds crazy after spending hours and hours but that solved my problem.
Good luck!