After a PC migration, SourceTree may show
fatal: detected dubious ownership in repository...for repositories copied from the old machine. I fixed the ownership mismatch by reassigning the target directory owner withtakeown.This comes from Git for Windows’ ownership protection: if the repository owner does not match the current Windows user, Git blocks the repository to avoid unintended execution. Treat it as a copied-directory ownership mismatch before assuming the repository itself is broken.
Open PowerShell as administrator and reassign the owner of the target directory. Replace
C:\githubwith the directory where you keep your repositories.takeown /F "C:\github" /R /D YAfter running it, SourceTree could open the target repository again. On shared PCs or directories that contain other users’ files, keep the target path as narrow as possible.
Related content
Text-first cards so you can decide what to read next.
The shortest steps for managing Node.js/pnpm with mise in a Windows VSCode + Git Bash environment
- PostPublished:
VALORANT Won't Launch After Enabling a WSL2 Environment
Notes from when VALORANT hit VAN9005 on a PC using WSL2 and Docker Desktop. In environments where they cannot coexist, switching between development and gaming with hypervisorcontrol was the practical answer.
What I learned from creating a Japanese localization config for Deadlock and having it used by 50,000 players.
My Samsung 990 PRO M.2 SSD sometimes stopped reading and writing during games and stayed missing for a while after a reboot. After updating its firmware to 8B2QJXD7 with Samsung Magician, it has not happened again so far.
A short record from when the Steam version of SAND: Raiders of Sophie failed with `Unexpected error occurred`. It started working after enabling administrator mode for `Sand_BE.exe` and rebooting the PC, but I have not isolated whether that setting alone fixed it.
