Free Download Manager Software For Windows 10
Hilke Mcnally
I have 2 instances of Windows Explorer opened in the task manager at random times. It happens when i restart my computer, use it for some time and after a while i notice the fans ramp up, i go to the task manager to find two processes of windows explorer, one is normal in my opinion which has 200-500MB RAM usage while the one is the problem, it consumes 2000MB of RAM (I have only 8 gigs ram so I am always anxious about that). I kill the process with the high ram usage and the computer runs normally. It is also worth mentioning that when i kill the process; the explorer and all the windows and task bar does not close or crash. The computer cools down and everything goes back to normal. The explorer.exe file is also normal. I was hoping that it might get fixed in the update but its still here.
Thank you for much for the suggestion but the issue still remains the same. I am fully updated and for some reason I can not find the feedback hub. It used to be in windows 10 but now when i search for it, it gives me "Feedback and Diagnostics" which has no option to report a bug, apparently there is a option to give feedback though, when you search something on the start menu; on the right top side there is an option to give feedback, just a little tiny button. I did that and lets see what happens...
I am sorry i could not try safe mode before, this time i used it for 30 minutes and the issue still persists. Even after closing all the windows the process remains in task manager with high memory use.
I have the same issue. After few seconds of starting windows, CPU1,3, and 5 go to 100% (I have intel i9-11900K). I know this by checking it on AIDA64 app.
When pressing ctrl+shift+escape the CPU usage goes back to normal, but if I close task explorer it goes back to 100% on CPU1, 3 and 5. This is why I am thinking it is a malicious virus.
So after I looked more, I found out in the details page that there are 2 "explorer.exe" running. If I terminate the second one the issue is solved.
Any idea how can I fix this once and for all without having to terminate explorer.exe each time I start windows? I tried Malware scans and everything stated above with no help.
@Reza_AmeriThank you for the response, I've tried everything you said, no files are corrupted and everything checks out but the error remains, even after windows update I thought Microsoft might fix the issue but it still remains.
For everyday work, Windows10 works great until October 2025 Microsoft provides support , updates go in parallel with Windows11 .
If you want to work, think about a clean installation of Windows10 -> write what you think?
Just about every developer has wanted a native package manager in Windows. That day is finally here. You are going to be able to winget install your way to bliss. One of the best parts is that it is open source. I had to pinch myself when I was able to winget install terminal, and then winget install powershell, and then winget install powertoys. You get the idea, and If you do not see an app you use, just create a new manifest, and submit a pull request.
Have you ever had to completely re-install all your apps and tools on your PC? How long did it take? How did you remember where to go to find, download, and install all your editors & IDEs, languages & runtimes, source control tools, etc.?
We have provided three different ways for you to get your hands on the Windows Package Manager. If you are a Windows Insider, you may already have it. First, you can head over to the open source GitHub repository for the client. Second, you can join any of the Windows Insider rings. Third, you can join the Windows Package Manager Insider program by providing your Microsoft Account (MSA) to Windows Package Manager Insider Program and request to be included in the preview. Either of the Insider programs will ensure you automatically receive updates as we progress from preview to general availability. After you have joined either Insider program, head over to the Microsoft Store and get the App Installer. The Windows Package manager will be available after you get the update.
We looked at several other package managers. There were several reasons leading us to create a new solution. One critical concern we had was how to build a repository of trusted applications. We are automatically checking each manifest. We leverage SmartScreen, static analysis, SHA256 hash validation and a few other processes to reduce the likelihood of malicious software making its way into the repository and onto your machine. Another key challenge was all the changes required to be able to deliver the client program as a native Windows application.
Windows Package Manager will support every Windows 10 version since the Fall Creators Update (1709)! The Windows Package Manager will be delivered with the Desktop App Installer when we ship version 1.0. If you are building software to run on Windows 10 you will have a simple way for your customers to install your software on billions of machines.
We have already talked with a few of the well-known package manager teams. Chocolatey has a vibrant community with a massive collection of applications, and a rich history supporting both open source and enterprise customers. Scoop provides a convenient way to allow software to be installed without the UAC popups. Ninite keeps an eye on updates for all the apps it installed. There are many others like AppGet, Npackd and the PowerShell based OneGet package manager-manager.
We have a long list of features we think you will like. Take a look at the list of issues we have already created on GitHub. Be sure to +1 any issues you feel strongly about. If you do not see something, and you would like us to consider it, just create a new issue.
Reasons listed are either already solved problems (just host your own MS packages in your repo and allow the user to add trusted repositories on their own, no need to scan everything like a gatekeeper), or issues with the underlying OS that would be a much much smarter focus (get the msix standard in a place where it can be an common interface for installs and support everything from random package managers to the Microsoft store). Instead they are just starting from scratch. This looks like its years away from being a package manager I could rely on.
Hoping the May release brings better stability to Services for Linux on Win 10 (like opening files from Linux filesystem in Windows native, without completely corrupting them). Full login & user shell support in WSL would also resolve a lot of the problems with alternate shells (fully supporting umasks, etc.).
This is SOOOOOO broken. Every 10 seconds I get a popup asking for a password. No reason. No indication of which account it's for, just a generic "provide a username and password". So I have no idea which repository it wants a password for or even what program is requesting it. No indication of whether the password fail or succeded, and after a while the box just reappears. Over top of stuff, in the middle of presentations, etc. This is effectively malware. This all started with the installation of SourceTree 2.0, so it's gotta be that.
The problem seemed to start for me when I added a new bitbucket account (academic) and wanted to use two accounts. I have had Source Tree 2.x for a long time and don't recall this headache. I agree the GUI is borked since we have no idea for which account or which operation the credintial manager is asking this information.
Tools > Options > Authentication seemed also to be helpful for me. I removed the Saved passwords that were stored and re-tried a push. That forced the GCM dialog, to which I supplied credentials for the repo that I was pushing to. The push was successful, and I saw also that a new entry in "Saved passwords" was created for that repo.
It seems weird, since I have OAuth for both accounts, and can browse my bitbucket.org repos (some of which are private) with no problem. Why doesn't push (or pull) use that same method to authenticate?
EDIT (20 June 2018): Recent changes to Bitbucket authentication has also meant that you must use your email (NOT your username) when logging in. Currently, logging in with your username is still accepted but seems to cause several issues ranging from this repeated login prompt issue to the "too many login attempts" error when pushing.
The majority of issues in Git Credential Manager for Windows have been fixed in recent versions. The latest version (1.12.0) released a couple days ago fixed the remaining issues I had with Bitbucket authentication.
The latest Git Credential Manager for Windows is included in the latest Git for Windows. Until Atlassian update their embedded version, you could install Git for Windows 2.14.0 and within SourceTree, click "Use System Git" in Options.
Just to pop in here and bump this thread, it's been marked resolved, but it isn't. I have tried all of the "fixes" in this thread, and the only one that stops the annoying pop ups is going back to 1.9. Something happened recently, because I was just using this same repo on github last week without the issue. I noticed I was using the system git, so I updated that, tried the embedded git, etc. I stopped that service, rebooted a few times, yadayada.
Beware, that SourceTree is going to prompt you to login one time for every repository (not account) it knows about (not just open tabs), when it feels like checking for changes for the first time after you completed the above steps and you have to login every time providing your password.
Regarding a temporary 'fix' for this using 2.x version (on Windows), what I did when that annoying pop-up came up, was opening Task Manager, see what processes are running, could spot "Git credential manger.exe" (can't remember exact name), closed SourceTree and renamed that to something like "Git credential manger.old", (so it couldn't run anymore) which 'fixed' the popups for me.
b1e95dc632