I have tried to uninstall OwnCloud Desktop. However the uninstaller can‘t locate the original installer in C:\Users\\****\AppData\Roaming\ownCloud\. The old installer is no longer available on the OwnCloud website. Updating first won't work since the program first tries to uninstall the old version and I end up in a cycle. Any idea?
[enter link description here][1]
There are several methods on this webpage, I would suggest you try method 3 as you don't have an uninstaller and can't even update.
[1]: http://www.uninstallhelps.com/how-to-uninstall-owncloud2.html
Related
I'm using Pop OS 20.4 and installed Unity Hub from its store (I think it just downloads the app image from the Unity website and installs it but I don't know).
I set a personal license and want to install the version 2020.1.15f1. As you can see on the next tab there is enough space to install it
Unfortunately I get this error message when trying to install it
at the bottom of the hub this toast message appears
Does someone know what's wrong here? I clearly have enough space on my disk.
I get the same error for other versions too.
Ok here is the solution that worked for me:
Instead of installing it from the Pop OS store I uninstalled this Unity hub version. I restarted my machine and installed the .appimage file from the official website. I copied that file into the root of my home directory. When executing this version there was no error for me.
The reason why it is showing this error is because there is not enough space in your root directory. Typically this happens when there is only a single partition (at least in my case). So a workaround for this is to create a folder in you HOME directory called tmp and running the UnityHub.AppImage file pointing to that tmp folder and the application gets ample amount of space to install. It looks something like this :
TEMP=~/tmp ./UnityHub.AppImage
You can go to this link for further details.
I am experiencing a problem with debugging in vscode just after the last update. There's something going on (https://github.com/Microsoft/vscode/issues/45657)
I'd like to check the previous version to see if my case is a problem here or in vscode but I can not find instructions on how to downgrade (I suppose it's possible)
Previous versions of Visual Studio Code can be downloaded here:
https://code.visualstudio.com/updates/
Pick the version you want from the list on the left, and then click on the download link for your OS as shown here:
You should disable auto update (as mentioned by Gregory in the comment) to prevent it from auto updating itself later upon restart. To do this, go to Preferences, Settings and then search for 'update'. Set it to 'none' as shown below:
Visual studio docs now have a section documenting all Url endpoints for downloading platform and archive specific downloads.
For ex. for Windows 64 bit zip the download endpoint is : https://update.code.visualstudio.com/{version}/win32-x64-archive/stable
https://code.visualstudio.com/updates/ site is only Windows Installer.
If you want to download Zip Executable, you can download like this url pattern.
# <download version> is like 1.44.0
https://vscode-update.azurewebsites.net/<download version>/win32-x64-archive/stable
reference is this site.
https://github.com/Microsoft/vscode/issues/60933
And I try to download another site, and success to download. this site is linked in https://code.visualstudio.com/updates/
https://update.code.visualstudio.com/<download version>/win32-x64-archive/stable
I'm installing Doxygen on Windows 8.1 64 bit. At the end of installation, it throws up "unable to load isutils.dll" followed by an unable to set PATH error. I'm not bothered about the PATH error, I presume that is just a case of manually adding "C:\Program Files\doxygen\bin" to the PATH but what is the isutils.dll error about and how do I fix it?
Edited to add this:
I don't know if this is related or not but when I run the Doxygen wizard after installation and click the Select... button for scan/store directory, the application permanently shows the busy icon and stops responding, I have to break out of it using Task Manager.
I got a response on the Doxygen mailing list from Dimitri van Heesch, the developer of Doxygen. He said that this appeared to be a glitch in the installer script which he has fixed. I downloaded the new version and it installed with no issues.
When trying to debug a Metro project from VS, I came across this error:
DEP0700 : Registration of the app failed. Another user has already installed a packaged version of this app. An unpackaged version cannot replace this. The conflicting package is PACKAGENAME and it was published by CN=some Guid. (0x80073cf9)
But I have already uninstalled the app from the Start page, also, I can confirm that there is no entry left in Add/Remove program.
And since the access to the "%PROGRAMFILES%\WindowsApps" folder where the app files reside in is blocked, so I have no way to see if the app is still there.
However, I can still find many 'PACKAGENAME' occurances in the registry.
How to diagnose this? How to get rid of the "packaged version" so I can start debugging from VS?
Try installing the app from the windows store again, and then uninstall it from the start page. It appears that when Visual Studio does the uninstall it doesn't do it right.
1) Go to your Package.appxmanifest file in your solution
2) Go to the identity tag.
<Identity Name="xxxxxxx-yyyy-zzzz-tttt-bbbbbbbbbbbbb"
Publisher="CN=bigbob"
Version="1.0.0.0" />
3) Change the value of the Identity Name (Ex from ...bbbbb to ...bbbbc)
4) Rebuild and run
Source:
http://www.sempf.net/post/MetroUIAnother-user-has-already-installed-an-unpackaged-version-of-this-application.aspx
Are you sure you didn't just unpin the app? Try doing a search for it and see if it is still there.
I find a solution to the problem. It's said it is a "staged package" that does not show up in my start page so I can not uninstall it in normal way. I follow the steps, and successfully get rid of that "un-uninstallable" :) package.
This blog post was helpful, although after an hour or so of troubleshooting it turns out that I had indeed installed the package under another user account. After switching accounts and uninstalling from the start screen it worked fine.
I haven't been able to find any resources on how to do this.. Anyone have any ideas or resources?!
I've tried changing the ./configure options and I'm solving things one at a time but it seems like this method could take forever.. My current error is..
checking for jpeg_read_header in -ljpeg... no
configure: error: Problem with libjpeg.(a|so). Please check config.log for more information.
I'm running Snow Leopard.
Any help would be great,
Matt Mueller
I know this is an old question- but still relevant.
I'm updating my MAMP and am keeping up to date on PHP's stable releases by using a guide I found at davidgolding.net
The Guide goes as follows:
First, run the
phpinfo()
function in a PHP script on your localhost or go to PHPMyAdmin and hunt down the configuration page. You should see a large chunk of configuration markup at or near the top:
'./configure' '--with-mysql=/Applications/MAMP/Library'
'--with-apxs2=/Applications/MAMP/Library/bin/apxs'
'--with-gd' '--with-jpeg-dir=/Applications/MAMP/Library'
'--with-png-dir=/Applications/MAMP/Library' '--with-zlib'
'--with-freetype-dir=/Applications/MAMP/Library'
'--prefix=/Applications/MAMP/bin/php5' '--exec-prefix=/Applications/MAMP/bin/php5'
'--sysconfdir=/Applications/MAMP/conf/php5' '--with-soap'
'--with-config-file-path=/Applications/MAMP/conf/php5'
'--enable-track-vars' '--enable-bcmath' '--enable-ftp' '--enable-gd-native-ttf'
'--with-bz2=/usr' '--with-ldap' '--with-mysqli=/Applications/MAMP/Library/bin/mysql_config'
'--with-sqlite' '--with-ttf' '--with-t1lib=/Applications/MAMP/Library'
'--enable-mbstring=all' '--with-curl=/Applications/MAMP/Library' '--enable-dbx'
'--enable-sockets' '--enable-bcmath' '--with-imap=shared,/Applications/MAMP/Library/lib/imap-2006i'
'--enable-soap' '--with-kerberos' '--enable-calendar'
'--with-pgsql=shared,/Applications/MAMP/Library/pg' '--enable-dbase'
'--enable-exif' '--with-libxml-dir=/Applications/MAMP/Library'
'--with-gettext=shared,/Applications/MAMP/Library' '--with-xsl=/Applications/MAMP/Library'
'--with-pdo-mysql=shared,/Applications/MAMP/Library' '--with-pdo-pgsql=shared,/Applications/MAMP/Library/pg'
'--with-mcrypt=shared,/Applications/MAMP/Library' '--with-openssl'
Copy and paste this whole chunk into your text editor and remove the single quotes (search and replace should do it). Look for the flag
--with-pdo-mysql=shared,/Applications/MAMP/Library
and replace it with:
--with-pdo-mysql=/Applications/MAMP/Library
If you don’t do this, you might end up with an error.
ld: symbol(s) not found
Finally, add the following flag to the end:
--without-iconv
After you have downloaded the latest PHP release of your choosing from PHP Sources Snapshots,
cd
to the downloaded directory in Terminal. Paste your reformatted configuration string (all of it, including the beginning ./configure command) and run it.
After the configuration phase is finished, run:
$ make
$ sudo make install
Relaunch MAMP, and you’re good to go.
The current version (1.9) of MAMP / MAMP PRO includes PHP 5.3 and is available on the MAMP download page.
This is bound to cause a lot of headaches. The simplest solution is to navigate over to the mamp website and grab the latest version of the application. Download it, hit the install button and you will find your php version has been updated to the latest version...
Hope this helps, I spent quite a bit of time fiddling about with upgrading PHP before I actually looked :S
I don't know if MAMP has changed its configuration in the last few years but none of the solutions here helped me. What I did, and what worked right away was:
Download the PHP version you want from MAMP
Unzip it and move the new PHP folder into the MAMP/bin/php folder where you will see other subfolders with names like php5.3.7
Restart MAMP
Go to the PHP panel under Server in MAMP and choose the new verion of PHP from the drop menu
Start MAMP.
reinstall whole MAMP is very safe. You dont even need to take a copy of old MAMP. the new install does it on its own. just feel free to download new MAMP and click install. only care u need to take is this
Edit httpd.conf and open up line to include vhosts.conf and copy old vhosts.conf from old MAMP folder.
Goto MAMP Download page
then choose
an update from the Heading
"Additional PHP versions for MAMP PRO 2.2"