I make sure all of processes of VS Code have exited, but I can’t delete the bin directory.
I tried many tools to find which process is using the directory, but none of them reported.
The problem occurs on all of my Windows devices and I need to manually update each time.
This link suggests a workaround might be to stop Skype for Business:
https://github.com/Microsoft/vscode/issues/60697
Notes:
Different users had to close Skype for Business, SkypeBridge, or even f.lux (?)
Per the link, you can use Windows Process Explorer to determine which apps are holding "bin" open
In my case it was Teams, and found that by searching for Skype in Windows Process Explorer. Killed it and the update went smoothly.
Related
I'm trying to install moodle4mac on Catalina via a .dmg file. The .dmg file mounts okay. However, when I try to drag the MAMP folder to the Applications folder, I get the message "The operation can’t be completed because you don’t have permission to access some of the items."
When install dialog is showing 4 folders;
.DocumentRevisions-V100
.TemporaryItems
.Trashes
.fseventsd
The first three have no go signs on the folders suggesting that these are the problematic ones. I have checked the read/write permissions of the Applications folder, which looks fine. I have also run sudo spctl --master-disable which gives me the opportunity to download apps from anywhere, but this does not make any difference.
Any pointers greatly welcome!
Okay. It turns out the culprit was Sophos Home Antivirus. There was no indication in any of the error messages that Sophos was blocking this, hence I did not put two and two together. However, a warning message about the mounted volume popped up this morning, and I was able to trace this back to Sophos. It would be great if Sophos / MacOS could provide more detailed messages regarding such errors in future.
I see that there are way to Get Get-AppxPackage or Remove Remove-AppxPackage UWP app from windows 10 using PowerShell.
I am wondering if there is a way to reset a UWP app? I require it for automated testing, I would rather reset the UWP app than uninstall and install again, as that would slow down the testing.
If you're looking to clear your package's ApplicationData then you want
appdata = Windows.Management.Core.ApplicationDataManager.CreateForPackageFamily(pkgfamilyname)
appdata.ClearAsync()
See MSDN for ApplicationDataManager.CreateForPackageFamily() and .ClearAsync()
Powershell has no 'await' affordance last time I looked (though it's been a while) so not so viable. If you're looking to muck with applicationdata you may find APPDATA.EXE handy. You can probably guess why I wrote it... :P For instance
APPDATA.EXE Clear foo.bar_1234567890abc
If you're looking to reset a package to its initially installed state, then no, there is no API other than uninstall + install
Remove-AppxPackage foo.bar_1.2.3.4_x86__1234567890abc
Add-AppxPackage foobar.msix
Settings' Reset option for an installed package essentially does that just slightly more efficiently. You're still going thru the full deregister and uninstall the package and then install and register it for the user so it may not be instantaneous. But that's the only way to truly reset a package to its initial state. Windows has various forms of user data associated with a package (ApplicationData, IndexDB, more) as well as system state cribbed and wired up when a package is installed for a user (what is the package, where's it live, that the user has it, that it's status is not tampered or otherwise unhealthy, more). The only way to truly 'reset' that to the initial state is a full remove then add.
If you just need to wipe appdata then .ClearAsync is the ticket.
I am not aware of any command that would do that for you (except for the UI available in Settings app). However, you may write a PowerShell script that would clear up the application data files in the app's folder (this is not an official solution, but seems to work based on my trials).
Go to
C:\Users\{your_username}\AppData\Local\Packages\
And find your app's folder there. There are several folders containing the application state.
The nuclear option is to just delete all the folders. Then the app will crash once on startup, then the system will automatically reset it and restore the folders.
The less invasive option I have now tried seems to be to keep the folders and just delete their content, except for the AC folder, which seems to be system protected. When I tried this with my app, it launched successfully without crashing and system recreated the state files anew on its own.
The rest of application files lives in C:\Program Files\WindowsApps, but those are just application DLLs and content files and are read-only, so they should not affect the app state at all.
You may want to perform additional deletion if you use a shared publisher folder.
For windows 10 build 2004+ there seems to be a powershell command Reset-AppxPackage now.
UPDATE
My mistake, it is available from version 20175 onward. So, should be available in 20H2.
Recently forced upgraded to windows 10 by microsoft. Windows Start and cortana froze. Searched google and from powershell ran
Get-AppXPackage -AllUsers | Foreach
{Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
Now lot of my windows application have disappeared. They show up with #{AppPackageName} in taskmanager or when searched using cortana for example #{Microsoft.ZuneMusic_2019.6.15131.0_neutral_~_8wekyb3d8bbwe}. I can not remove these app using any command like
Tried to install store app manually and get error Merge Failure : error 0x80070003 : Cannot register the Microsoft.WindowsStore_2015.21.25.0_x64__8wekyb3d8bbwe package because there was a merge failure with the following file: C:\Program Files\WindowsApps\Microsoft.WindowsStore_2015.21.25.0_neutral_split.scale-100_8wekyb3d8bbwe\resources.pri
Full log below:
Now I understand that store app is not getting add because add process is causing error or merge failure with another package (?). The problem is get/Add-AppxPackage are resolving dependency of application with package-version: Microsoft.WindowsCalculator_10.1510.13020.0_neutral_split.scale-100_8wekyb3d8bbwe
AND/OR
Microsoft.WindowsCalculator_10.1510.13020.0_neutral_split.language-hi_8wekyb3d8bbwe
My laptop c:\program files\windowsapp only has Microsoft.WindowsCalculator_10.1510.9020.0_neutral_split.scale-100_8wekyb3d8bbwe (not diff in version 13020 and 9020). Note: The version no on app is 13020 but dependent package on drive is 9020.
Second package is missing from drive (Microsoft.WindowsCalculator_10.1510.13020.0_neutral_split.language-hi_8wekyb3d8bbwe).
How to get my calculator and windows store application back.
<1>Create a new user account and Log into the new account
<2>You can also try
Running the System File Checker by running
sfc /scannow
Download files from Windows Update to replace the corrupt ones by running
DISM /Online /Cleanup-Image /RestoreHealth
You may try the following, at your own risk.
I had the same issue after trying to reinstall the apps via that powershell thingy. Fixed it and returned the apps to their out-of-box state by first wiping everything from C:\Program Files\WindowsApps and C:\Users*\AppData\Local\Packages and then reinstalling Windows over itself from the tech bench ISO (from under Windows and keeping "traditional" apps and files in place, of course). I had to use the ISO because the media creation tool wasn't cooperative at all, throwing some error at me. Just in case, the aforesaid wiping didn't cripple the vitals like the immersive control panel or something else, just the typical no start menu/dead modern apps/no right click on the taskbar items.
By the way, the whole problem started after the 1511 update. Modern apps would refuse to remember their settings, and windows shell experience host would freeze for no reason, taking the start menu and things like volume control with it. I've had this Windows installation for a couple of years now, and the system has gone pretty smoothly through the 8.0-8.1-10 update process over that time, but that 1511 screwed something big time.
When I run the Windows Tray Notifier on my Windows 8 virtual machine, it remains stuck on a "logged in" message if I hover over the icon of the program in the system tray, and I can't do anything else other than force the shutdown with the Task Manager. I set the correct address where my TeamCity test server is running but it seems unable to connect to. Any help is appreciated.
Fixed it via the following steps:
Repaired via installer (this clears saved login data)
Logged into a different server running Teamcity 6.5.3 - this worked
logged out again and logged into our main teamcity server (running 7.1) - tray notifier is working again
Very strange! Above workaround would only work if you had access to a second server too.
EDIT: Two further workarounds have been posted on the thread I started on the Jetbrains forum, so I'll repost them here for the benefit of others.
Solution 1:
Kill running tray notifier in task manager
Open regedit, in HKEY_CURRENT_USER\Software\JetBrains\TeamCity\WindowsTray\Login, update the “S” property to http://192.168.1.1:8080 (substitute real ip address, without the quotes, trailing / seems to be important)
Open IE, go to team city site
Log in, checking “remember me”
While IE is open and connected to TeamCity, start up tray notifier.
Takes about 15 sec to change from “logging in” to connected.
Solution 2:
Open IE, select Internet Options, Security Tab, add the TeamCity server address to the trusted list.
Please note, I haven't personally tested either of these methods, just posting them here for information since others have found them to work. Hope this helps!
Since upgrading the server to 7.1.1 this issue hasn't reoccurred for me. Looks like it's been fixed as per Eugene's comment elsewhere on this thread.
This issue is definitely a bug in the tray notifier.
It isn't popping up login credentials, so
Log first into IE
Check remember me - try to save credentials
Close IE/Launch the notifier
It should be successful
Henry Wilson posted the answer in their forums. Hopefully it's fixed soon.
I had a similar problem, the only difference is that it was stuck in "Loading..." and not in "Logging in...".
I added a trailing slash to the URL in "HKEY_CURRENT_USER\Software\JetBrains\TeamCity\WindowsTray\Login" but it didn't help, so I deleted the whole tree "HKEY_CURRENT_USER\Software\JetBrains\TeamCity". After a restart of the application, it asked again for the URL.
I use 8.0.5 on the server. The tray notification reports "build NA" in the about window...
I have had this on:
Windows 7 - 64 bit,
TeamCity Pro 7.1 (build 23907)
All other effects are identical as above.
The suggestions above didn't work for me, but it did allow me to re-enter the server address.. still the problem persisted.
What worked for me was to remove then re-install in "Program Files" instead of the default "Program Files (x86)". There are a few reasons why this as-a-fix should be unnecessary, but it worked and I'm happy.
This worked for me:
Open the CI-Server URL in Internet Explorer
Log out from the CI-Server
Restart the Tray Notifier (maybe kill via Taskamanger)
Log in again
p.s. not sure if it is relevant, but for completeness:
I also added the CI-Server URL in the trusted sites in Internet Explorer → Internet Options (as mentioned in this answer: https://stackoverflow.com/a/12001721/1520422)
I'm running Windows Server 2008 with a Blackmagic Decklink card. Everything works fine with the GUI but when I try to start from command line it exits with an unknown error.
Any ideas?
Note: I have the desktop experience enabled.
Looks like a frequent problem that effects many FMLE users. Common suggestions include:
use the absolute latest version of FMLE
update DirectX
update all video and audio-related drivers
remove/rename startup.xml from "[volume]/Users/[user name]/AppData/Roaming/Adobe/Flash Media Live Encoder [version]/" so the program can get clean settings
There is also a small chance that tweaks to common security measures may help, such as disabling Data Execution Protection for all but essential OS files or exclude program directories in your anti-virus software (only if essential, of course!)
I found out what the problem was, apparently if the fmesessions.dat (C:\ProgramData\Adobe\Flash Media Live Encoder 3.2) gets large enough FMLEcmd.exe fails.