Windows 10: Windows Package Manager v0.2.3162 Preview released

Brink · Dec 2, 2020

This release improves the experimental list and upgrade commands by showing Add/Remove Programs (ARP) entries.

The default location for installer logs was moved to the same location as winget logs, thus allowing them to be collected by Feedback Hub. If you encounter a bug, just submit feedback [Windows]+[f] and the logs will be sent for us to be able to review what went wrong.

Trusted sources (like the Microsoft Community Package Manager Repository) will have downloaded files set to Zone 2. Other sources will have be set to Zone 3, and the file will be run through all local Anti-virus (AV) software by attachment execution services.

Read more: Release Windows Package Manager v0.2.3162 Preview . microsoft/winget-cli . GitHub

:)

Brink · Dec 2, 2020

Windows Package Manager Preview v0.2.2521 released

We have been humbled by all the positive support for the Windows Package Manager. You have taken us from zero to over one thousand packages in six months. This is an amazing start to the beginning of an open Windows catalog. Thank you!

Our newest feature is support for installing Apps from the Microsoft Store. Yes, you read that correctly. Our goal is to make it easier to install software on Windows. We also recently released tab completion in PowerShell, and a feature toggle. As we work towards building our 1.0 version I wanted to share the next few features along the roadmap. Our immediate focus is on rounding out critical features. These include list, upgrade, uninstall, and import/export.

I also wanted to share some thoughts we had leading up to Ignite in terms of future enterprise features. We will be enabling Group Policy support so IT professionals can ensure they have the ability to successfully manage their environments. Additional features included in the category of enterprise support are delivery optimization, metered networks, proxy support, and parallel downloads.

What’s New

Feature Toggle

If you would like to try out experimental features, use winget settings to open your default JSON editor. If you don’t have one I’d reccomend running winget install vscode. From there you can enable or disable features. I’ve included an example configuration below with our two experimental features for testing purposes (experimantalCMD, and experimentalArg) as well as the “experimentalMSStore” feature.

Experimental Feature Settings

Once you’ve enabled the experimentalCMD and the experimentalArg, execute winget experimental --arg to see an example. There is a little “Easter Egg” in the “flag”.

PowerShell autocomplete

You’re going to want to see this next feature in action on your machine. Head on over to the instructions and configure your PowerShell profile, I’ll wait. If the image below doesn’t play, please click on it.

I told you I’d wait. We don’t like unnecessary typing either. This quickly became my favorite way to figure out which versions of a package are available. Type winget[space][tab][space]pow[tab][space]-v[space][tab][tab][tab] and voila.

Microsoft Store

One of our most requested features was the ability to install Apps from the Microsoft Store. We’ve taken the first steps on this journey by adding a curated list of about 300 Apps to a new source. These apps are all free and rated E for everyone. Once you enable the experimental feature, we will automatically add the source for the store manifests. The search will span multiple sources to show results. Below, you will see results for winget search nightingale.

Next you will see the installation from the command winget install "Nightingale REST Client".

What’s Next

List

One of the critical features of a package manager is the ability to see what’s been installed. Our challenge here is to include Apps that may have been installed outside of the package manager and are available in the Control Panel or via Add Remove Software. We didn’t want to just consider what was installed via the Windows Package Manager. We will, however, keep track of what we installed so we can help you keep things upgraded to the current version.

Upgrade

Speaking of upgrade, wouldn’t it be nice if you could just winget upgrade powershell or winget upgrade and have all your apps upgraded. We thought so too. One of our more vocal (and helpful) community members (@megamorf) also pointed out you don’t always want a package upgraded. We’re going to give you the option to pin a package to a specific version, so it doesn’t get changed on you.

Uninstall

Sometimes you don’t need or want an app anymore. Generally, in my case, I want the space back on my C: drive. winget uninstall "some giant app" would come in handy. It would be cool if it could remove things that were installed outside of the package manager, so we’re going to see about getting that to work as well.

Import / Export

We couldn’t pass up the opportunity to perform a little more magic for the sake of convenience. It’s getting close to the time where I’ll be getting a new machine for work. I’m looking forward to be able to winget export packages.json from this computer and winget import packages.json on the new one. I’m looking forward to being able to share the results of that one with you.

How to get the Windows Package Manager

If you are a Windows Insider or part of our Package Manager Insider program, you should already have the latest version. Launch the store and check for updates if you’re an insider and you don’t have it. If you prefer to just download the client, head on over to GitHub releases page and take it for a spin. You can also join the Windows Package Manager Insider Program if you’d like automatic updates from the store, and you want to run on the released version of Windows 10.

Be sure to check out the GitHub client issues and add a “+1” to any features you’d really like to see.

Demitrius Nelon

Senior Program Manager
Click to expand...

Source: https://devblogs.microsoft.com/comma...iew-v0-2-2521/

Tweet

— Twitter API (@user) View on Twitter

Tommy · Dec 2, 2020

Type Cover 2 not working with WIndows 10 (Release)

So, after suggesting checking for firmware updates, it does appear there was a firmware release July 23, 2015 that resolves this issue. The step-by-step directions as well as the firmware release history for the Surface Pro 2 can be found here.

Brink · Dec 2, 2020

Microsoft releases Secret Management Preview 2 module for PowerShell

We are excited to release a second preview of the Secret Management Module. Thanks to the tremendous feedback we received from the first preview release of this module, you will notice a number of breaking changes to the module. This release is still a preview release meaning that it is not feature complete, future releases will face breaking changes, and we are still iterating based on your feedback. It is important to also note that this version of the module is still Windows only as we are currently implementing Linux support which we hope to make available in the next preview release (and MacOS support after). Please note that because of the breaking changes this release requires a complete replacement of the Secret Management module and any extension modules. Additionally, any existing built in local vault secret can no longer be retrieved and must be re-saved.

How to Install Secret Management Preview 2

If you did not install our first preview release, open any PowerShell console and run:

Install-Module Microsoft.PowerShell.SecretManagement -AllowPrerelease

If you installed our first preview release you will want to first remove any secrets from the LocalDefaultVault. Based on feedback we changed the naming convention for secrets stored in CredMan, therefore previous secrets stored in the local vault will no longer be visible after the new version of the module is installed. (Although the user can still view/remove the old secrets via CredMan UI.) Next you will want to run Uninstall-Module Microsoft.PowerShell.SecretsManagement, this extra step is a result of the change we made to the name of the module. Finally you can run the above command Install-Module Microsoft.PowerShell.SecretManagement -AllowPrerelease to install the latest preview release of the module.

Changes in Secret Management Preview 2

New Module Name

We have removed the plurality in the module name to Mirosoft.PowerShell.SecretManagement in order to be consistent with the cmdlet name and to align with PowerShell naming conventions.

New Cmdlet Names

In addition to renaming the module, we have also removed plurality in the cmdlets. The available cmdlets in the module are now:

Code:

# Registering extension vaults
Register-SecretVault
Get-SecretVault
Unregister-SecretVault
Test-Vault # new cmdlet in this release

# Accessing secrets
Set-Secret # this cmdlet replaces Add-Secret
Get-Secret
Get-SecretInfo
Remove-Secret
Click to expand...

You will notice we renamed the Add-Secret cmdlet to be Set-Secret. This change was based on user feedback that this name better conveyed the intention of the cmldet.

You will also notice that we have added a Test-Vault cmdlet, this change allows vault extension owners to check that the vault is properly configured at registration time.

Other Changes

Set-Secret now has a default parameter set that takes SecureString secret input type. This way Set-Secret will always prompt safely for a SecureString. String secret types can still be passed via parameter or pipeline, but default will be SecureString.

Code:

PS> Set-Secret -Name MyStringToken
cmdlet Set-Secret at command pipeline position 1 Supply values for the following parameters:
SecureStringSecret: **********

# Set string secret directly
Set-Secret -Name MyStringToken -Secret $token
Set-Secret -Name MyStringToken -Secret 'MyToken'
# Set string secret via pipeline
$token | Set-Secret -Name MyStringToken -NoClobber
Click to expand...

Added SecretInformation class used to return information from Get-SecretInfo in a uniform way.

Changed CredMan naming prefix to ps:SecretName.

Added vaultName to all vault extension functions.

Fixed additionalParameters parameter in SecretManagementExtension abstract classes.

Fixed return byte[] bug in example test script extension.

In coordination with these changes we have also updated our tests and example scripts.

Next Steps

As we move towards a GA release later this year, we are using a GitHub Milestone to track issues we plan to fix. The two major work items that we are currently working toward are:

Linux Support (via keyring)

MacOS Support (via keychain)

Support and Feedback

For support on the module, feedback, or reporting a bug, please open an issue in the PowerShell/modules repo with “(Secrets Management)” specified in the issue title.
Sydney Smith, PowerShell Team
Click to expand...

Source: https://devblogs.microsoft.com/power...iew-2-release/

Windows 10: Windows Package Manager v0.2.3162 Preview released

Windows Package Manager v0.2.3162 Preview released

Windows Package Manager v0.2.3162 Preview released

Windows Package Manager v0.2.3162 Preview released

Windows Package Manager v0.2.3162 Preview released - Similar Threads - Package Manager 3162

PowerShell 7.2.0 preview 2 released

Windows Package Manager Preview v0.2.2521 released

Windows Package Manager v0.2.2521 Preview released

Microsoft announces Windows Package Manager Preview for Windows 10

Windows Package Manager Preview | Windows Command Line

Powershell 7.1 preview 2 is released

Microsoft releases Secret Management Preview 2 module for PowerShell

Visual Studio 2019 v16.4 Preview 2 released

Preview release.