Windows 10: Ran Normal PowerShell Command- Scriptblock Logging Says Things About 'Untrusted Repository'?

JamLow · Nov 5, 2023

I ran "Get-InstalledModule" to check if there are any modules installed, to which it returned empty and indicated that there were no installed modules, which is how it should behowever, I looked in the PowerShell > Operational log in Event Viewer > Applications and Services > Windows, and saw around 4 Warning events. after combing through what they said, I'm kind of concernedI've run 'Get-InstalledModule' several times today, and these Warning scriptblock events happen in response to that command. They mention things like this;"UnableToUninstallAsOtherScriptsNeedThisScript=The script

:)

Kursah · Nov 5, 2023

PowerShell instead of Commandline in Creators Update

Interestingly enough my personal laptop just got the update...and still has Command Prompt listed, not PowerShell...

Edit: Not that it matters...I use both regularly. *Toast :toast:

Brink · Nov 5, 2023

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 · Nov 5, 2023

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: Ran Normal PowerShell Command- Scriptblock Logging Says Things About 'Untrusted Repository'?

Ran Normal PowerShell Command- Scriptblock Logging Says Things About 'Untrusted Repository'?

Ran Normal PowerShell Command- Scriptblock Logging Says Things About 'Untrusted Repository'?

Ran Normal PowerShell Command- Scriptblock Logging Says Things About 'Untrusted Repository'?

Ran Normal PowerShell Command- Scriptblock Logging Says Things About 'Untrusted Repository'? - Similar Threads - Ran Normal PowerShell

i accidentally ran a powershell code COde is: powershell -NoProfile -Command "mshta...

i accidentally ran a powershell code COde is: powershell -NoProfile -Command "mshta...

Every command of PowerShell is broken saying "command was found in the module"

Every command of PowerShell is broken saying "command was found in the module"

Every command of PowerShell is broken saying "command was found in the module"

Ran Normal PowerShell Command- Scriptblock Logging Says Things About 'Untrusted Repository'?

Ran Normal PowerShell Command- Scriptblock Logging Says Things About 'Untrusted Repository'?

Powershell command

powershell commands