Windows 10: I just cloned a repo from github using git but it dosn't show in file explorer

Adwait Sadangi · Apr 1, 2025

I have also checked for hidden files but there are none.

:)

Aditya Jambhale · Apr 1, 2025

User profile corruption after cloning git repository

My user profile is getting corrupted after cloning the git repository.

While the cloning is in progress there are scripts in the repo which tries to access 'c:\users\username\appdata\roaming' to save some data.

In the console log, getting the error as 'c:\users\username\roaming' folder doesn't exist and cloning stops. The location 'c:\users\username' folder is not accessible as "You don't currently have permission to access this folder"
error occurs (User has administrator privileges) This happens only after cloning the repository. Once the user profile is corrupt after sign in a temporary user profile is created and "We can't sign in to your account" error occurs.

Before the cloning I am able to access these folder without any errors and can sign in to the machine without any issues.

To recreate the corrupted user profile following these steps and the solution works.

https://webmakers.co.nz/delete-temp-user-profile-windows-server-2008-later/

After this whenever tried cloning to repo same user profile corruption issue persists.

Machine Details:

OS: Windows Server 2016

Git: 2.18.0

This issue is observed for couple of guys in team but works fine for others as a regular process of git cloning. Cross verified the system configuration and git repository privileges as well.

Brink · Apr 1, 2025

The Microsoft PowerShell-Docs repo is moving

On January 16, 2019 at 5:00PM PDT, the PowerShell-Docs repositories are moving from the PowerShellorganization to the MicrosoftDocs organization in GitHub.

The tools we use to build the documentation are designed to work in the MicrosoftDocs org. Moving the repository lets us build the foundation for future improvements in our documentation experience.

Impact of the move

During the move there may be some downtime. The affected repositories will be inaccessible during the move process. Also, the documentation processes will be paused. After the move, we need to test access permissions and automation scripts.

After these tasks are complete, access and operations will return to normal. GitHub automatically redirects requests to the old repo URL to the new location.

For more information about transferring repositories in GitHub, see About repository transfers.

If the transferred repository has any forks, then those forks will remain associated with the repository after the transfer is complete.

All Git information about commits, including contributions, are preserved.

All of the issues and pull requests remain intact when transferring a repository.

All links to the previous repository location are automatically redirected to the new location.

When you use git clone, git fetch, or git push on a transferred repository, these commands will redirect to the new repository location or URL.

However, to avoid confusion, we strongly recommend updating any existing local clones to point to the new repository URL. You can do this by using git remote on the command line:

git remote set-url origin new_url

For more information, see Changing a remote’s URL.

Which repositories are being moved?

The following repositories are being transferred:

PowerShell/PowerShell-Docs

PowerShell/powerShell-Docs.cs-cz

PowerShell/powerShell-Docs.de-de

PowerShell/powerShell-Docs.es-es

PowerShell/powerShell-Docs.fr-fr

PowerShell/powerShell-Docs.hu-hu

PowerShell/powerShell-Docs.it-it

PowerShell/powerShell-Docs.ja-jp

PowerShell/powerShell-Docs.ko-kr

PowerShell/powerShell-Docs.nl-nl

PowerShell/powerShell-Docs.pl-pl

PowerShell/powerShell-Docs.pt-br

PowerShell/powerShell-Docs.pt-pt

PowerShell/powerShell-Docs.ru-ru

PowerShell/powerShell-Docs.sv-se

PowerShell/powerShell-Docs.tr-tr

PowerShell/powerShell-Docs.zh-cn

PowerShell/powerShell-Docs.zh-tw

Call to action

If you have a fork that you cloned, change your remote configuration to point to the new upstream URL.

Help us make the documentation better.

Submit issues when you find a problem in the docs.

Suggest fixes to documentation by submitting changes through the PR process.

Sean Wheeler
Senior Content Developer for PowerShell
sdwheeler - Overview
Click to expand...

Source: The PowerShell-Docs repo is moving | PowerShell Team Blog

Brink · Apr 1, 2025

The Microsoft PowerShell-Docs repo is moving

On January 16, 2019 at 5:00PM PDT, the PowerShell-Docs repositories are moving from the PowerShellorganization to the MicrosoftDocs organization in GitHub.

The tools we use to build the documentation are designed to work in the MicrosoftDocs org. Moving the repository lets us build the foundation for future improvements in our documentation experience.

Impact of the move

During the move there may be some downtime. The affected repositories will be inaccessible during the move process. Also, the documentation processes will be paused. After the move, we need to test access permissions and automation scripts.

After these tasks are complete, access and operations will return to normal. GitHub automatically redirects requests to the old repo URL to the new location.

For more information about transferring repositories in GitHub, see About repository transfers.

If the transferred repository has any forks, then those forks will remain associated with the repository after the transfer is complete.

All Git information about commits, including contributions, are preserved.

All of the issues and pull requests remain intact when transferring a repository.

All links to the previous repository location are automatically redirected to the new location.

When you use git clone, git fetch, or git push on a transferred repository, these commands will redirect to the new repository location or URL.

However, to avoid confusion, we strongly recommend updating any existing local clones to point to the new repository URL. You can do this by using git remote on the command line:

git remote set-url origin new_url

For more information, see Changing a remote’s URL.

Which repositories are being moved?

The following repositories are being transferred:

PowerShell/PowerShell-Docs

PowerShell/powerShell-Docs.cs-cz

PowerShell/powerShell-Docs.de-de

PowerShell/powerShell-Docs.es-es

PowerShell/powerShell-Docs.fr-fr

PowerShell/powerShell-Docs.hu-hu

PowerShell/powerShell-Docs.it-it

PowerShell/powerShell-Docs.ja-jp

PowerShell/powerShell-Docs.ko-kr

PowerShell/powerShell-Docs.nl-nl

PowerShell/powerShell-Docs.pl-pl

PowerShell/powerShell-Docs.pt-br

PowerShell/powerShell-Docs.pt-pt

PowerShell/powerShell-Docs.ru-ru

PowerShell/powerShell-Docs.sv-se

PowerShell/powerShell-Docs.tr-tr

PowerShell/powerShell-Docs.zh-cn

PowerShell/powerShell-Docs.zh-tw

Call to action

If you have a fork that you cloned, change your remote configuration to point to the new upstream URL.

Help us make the documentation better.

Submit issues when you find a problem in the docs.

Suggest fixes to documentation by submitting changes through the PR process.

Sean Wheeler
Senior Content Developer for PowerShell
sdwheeler - Overview
Click to expand...

Source: The PowerShell-Docs repo is moving | PowerShell Team Blog

Windows 10: I just cloned a repo from github using git but it dosn't show in file explorer

I just cloned a repo from github using git but it dosn't show in file explorer

I just cloned a repo from github using git but it dosn't show in file explorer

I just cloned a repo from github using git but it dosn't show in file explorer

I just cloned a repo from github using git but it dosn't show in file explorer - Similar Threads - cloned repo github

I just cloned a repo from github using git but it dosn't show in file explorer

Why folders's icons in the explorer dosn't appears?

Debloater from github just deleted about a years worth of important files

just cloned a drive and files are all there, BUT used space differs?

New Windows 10 Developers Landing Page and GitHub Repo

Github integration into File Explorer

Microsoft is renaming UI Fabric GitHub repo to Fluent UI

Using GIT GUI on Microsoft

GitHub announces unlimited free private repos and unified Enterprise