4 ms·

I don't think I have any shell extensions installed. I did allow git, 7zip, and clion to add themselves to the right click context menu, but I don't think that

• mehrdadn 7y ago
  > I did allow git, 7zip, and clion to add themselves to the right click context menu, but I don't think that counts as a shell extension? They do count, but whether or not they're relevant depends on whether they're triggered. e.g. if you never right-clicked, then 7-zip probably doesn't count. Although 7-zip also installs drag-drop handlers, so it's not just right-clicking, and I'm not sure when the others get triggered. > I'm using git with the terminal editor that they recommend to you in the git for Windows installation, I think it's called git with bash? It could have been some type of issue there rather than Microsoft being at fault. But that terminal editor is (or at least was) the recommended option presented to you in the git installer, so shrugs. Hm, somehow I feel neither of them is related. How likely is it that the name wasn't unique after your rename? Did you type in gibberish or something that could plausibly exist? Note that if you were ever trying to remove e.g. a directory that was the current working directory of any running program (like your terminal or anything else), that'd fail. It's possible that there's some bug that makes you think it's succeeding, and therefore making you think that the folder no longer exists. But hard to say with the current info.
  • suby 7y ago
    > Hm, somehow I feel neither of them is related. How likely is it that the name wasn't unique after your rename? Did you type in gibberish or something that could plausibly exist? I only have my memory to go by so this could be faulty, but if I remember correctly I was trying to copy a public repository into an empty folder. I simply called git clone url. When that failed, considering the error message I got, I then entered in the clone command with a random string of characters for the destination name, again in the same empty folder. When that failed, I closed the terminal, opened a new one on my desktop, and that failed, too. Restarting fixed it. I encounter a lot of weird issues with Windows. I'm not sure if it's my hardware combination, or what. The hardware itself contains my Linux install, which never gives me an issue, so I doubt it's faulty hardware. At one point I assumed I had installed from a corrupted ISO or something, so I downloaded a new ISO and reinstalled. Problems persisted. It's entirely possible that some program that I typically install causes issues, but I can't imagine what program that would be. Practically the only thing on my Windows partition is visual studio (c++ and c# tooling), clion, 7zip, WSL (could be this, I suppose), an installation of ruby, and Sublime Text. I know at one point Microsoft was saying that CCleaner was causing problems, but I'm not using anything like that.
    • mehrdadn 7y ago
      I see, thanks for elaborating! Yeah that's really bizarre. Especially because, if you give a random destination name for git clone, it shouldn't matter at all whether the current folder is empty or not -- the repository's will be in a subfolder after all. The question here is what is the actual error you got in that case -- was it again something about the target folder not being empty (despite being random), or something else entirely? If it's the former, then I have no clue haha. But if the error might've been different this time, then that might explain it. Regarding WSL, it shouldn't be related unless you'd actually launched it sometime between when the incident occurred and the most recent boot before then. But even then, I can't imagine how cloning into a new folder with a random name could possibly trigger a WSL issue of this sort. Otherwise, the only things I can imagine are clion or Sublime Text (whichever have shell extensions)? Only because I don't use either, so I have no idea what functionality they might incorporate into the shell. If I had to take a wild guess, it might be auto-scanning inside folders (for whatever reason) and keeping handles open that prevent file deletion and such? But again, unlikely given that so many people use it, and given that even Visual Studio doesn't need to scan like that. In terms of weird issues more generally -- yeah I think it's pretty unlikely your case is hardware-related. I do have to say Windows 8.1 seemed more stable than 10. Especially on 1909, I've gotten some 3-4 BSODs over the past few weeks, which is way more than I used to get since before the update, and I've been pretty clueless as to why. But on the other hand, I'm pretty impressed that the file system is still intact, and even completely unaffected by most BSODs, and so barring the inconvenience of the reboot, I rarely have problems. Whereas, with Linux, I have a different variety of problems :P like I upgrade the OS and my package dependencies break, or I upgrade packages and now have to figure out how to fix configs and services that broke, or I want to install an older version of some program and now my afternoon is gone, or I run a script and it suddenly wrecks my system because I happened to have a space in my path, or something goes wrong and the file system suddenly gets a ton of errors (generally the FS seems much more fragile than on Windows)... well I can keep going :-)