Blog. Weekend Scripter: Working with Windows Libraries – Hey, Scripting Guy! Blog Remove a directory from the Library and close the ShellLibrary object

Googled it

Attachment 2******3

....
Another problem has appeared: applications from the store cannot be installed, and all the ones I tried gave this error. Is there any way to treat this?

Message from Grunger:

When opening any library (videos, documents, music, etc.), the error window “The library “Videos.library-ms” has stopped working” pops up.

Googled it
C:\Users\....\AppData\Roaming\Microsoft\Windows\Libraries\Do cuments.library-ms
C:\Users\....\AppData\Roaming\Microsoft\Windows\Libraries\Mu sic.library-ms
C:\Users\....\AppData\Roaming\Microsoft\Windows\Libraries\Pi ctures.library-ms
C:\Users\....\AppData\Roaming\ Microsoft\Windows\Libraries\Vi deos.library-ms

deleted these files, then right-click on “Libraries” - restore standard ones. It helped.

Defender - definitely just a firewall? Otherwise, it catches my autoruns and keygens...
Attachment 2******3

Well, I guess not. It looks too much like Microsoft security essentials, it looks like it really is an antivirus.

An interesting point is that on Windows 8 you cannot run Metro applications using the built-in administrator account.

What will happen to the trial version when the eight goes on sale?

To find out the end date of the trial version, enter winver and you will see:

Trial version. Deadline expires 01/16/2013 2:59

That is, after celebrating the New Year and sub-New Year holidays, Microsoft will also give out its “gift” on the screen...

[collapse]

Attachment 2******3

When the final version comes out, I won’t need the trial version anymore; I’ll just take tokens from the trial version so that I can use the product normally without having to buy a license.

Still, no matter how much I read that eight is already stable and you can install the main OS, it’s not stable at all. I installed it on a netbook, and when I exit sleep mode, all network adapters are turned off and there is no way to turn them on anywhere, they stupidly disappear, and along with them all the settings. Only rebooting the OS helps. The ATI Catalyst driver, written for Windows 8, already managed to yell that an exception had occurred at the address, and today, out of the blue, a BSD appeared when I was reading a message on the forum. And this is only three days of work. I haven’t installed any programs yet, just the driver for the video drive and that’s it. All other firewood is pre-installed. When there was seven on the netbook, even if there was one error or malfunction, I’m already silent about BSoD.

Windows 8 Codecs 1.1.1 is the final set of codecs from the developers of Win7codecs, designed for installation on the new Windows 8 operating system. It is required to watch videos. Currently, Windows 8 Codecs is the only such solution designed to work in the new OS environment. The package is an automated tool designed to install basic codecs and decoders. Unlike its older brother, it does not contain any additional players and does not change the default system file associations. Additionally, upon installation, it will automatically remove the already installed codecs and replace them with the bundled ones for better compatibility.

Changelog:
- improve subtitles /LAV-VC1
- update Intel QuickSync r35
- update LAV filters 50.5+
- update MediaInfo

OS: Windows® 8
Interface language: Russian

By the way, for those who do not install applications from the store, do not update them, just like Windows itself: go to the website is74.ru and look for a free update in the connection instructions for setting up.

Well, or - to be shorter - write the following DNS addresses in the connection properties of ImmediateInternet in the properties of Internet Protocol version 4 (TCP/ipv4)

78.29.2.23
78.29.2.24

I need some programs to run with administrator rights. For example, total commander, fubar2000. In the shortcut properties, on the "Compatibility" tab, I indicated this. Now when you start the program, UAC prompts you. Is it possible to get rid of this?

Mocosh.Documents Library v1.1

Summary: Microsoft PFE Chris Wu talks about working with Windows libraries using PowerShell.

Microsoft Scripting Guy, Ed Wilson is here. Today we welcome back Microsoft PFE guest blogger Chris Wu. You can check out Chris's past posts. Chris, the keyboard is yours.

Being involved in the Windows 7 deployment process, one of the questions I asked myself was how to manage Libraries. Windows libraries allow you to organize files regardless of their physical location. By default, Windows has 4 libraries: Documents, Music, Pictures and Videos. Each of them includes corresponding user profile and public profile folders.

Libraries are where programs like Windows Media Player and many Windows Store apps for Windows 8 primarily look for files. In a corporate environment, it may be convenient to include a group shared folder located on the server in the library instead of to redirect the user's My Documents directory. Unfortunately, library settings are located in Library Description (*.library-ms) files, and there are no Group Policy settings to control them. Thus, you have to distribute pre-configured library-ms files to users' computers, which is quite inconvenient.

And again, Windows PowerShell comes to the rescue.

The Windows Shell API allows you to programmatically configure libraries, and the Windows API Code Pack for the Microsoft .NET Framework allows you to use .NET classes that you can work with quite comfortably from Windows PowerShell. To work with Libraries, we need 2 DLLs from the API Code Pack. Just download the current release and extract Microsoft.WindowsAPICodePack.dll and Microsoft.WindowsAPICodePack.Shell.dll (both located in the binaries folder) to some local directory (for example c:\tools).

After this we will be able to perform the following tasks:

Get a list of Libraries existing on your computer

::Libraries | Select-Object Name,ParsingName

Get Library settings

The second parameter of the Load method specifies whether to include the Library in read-only mode. Since we are going to make changes to the library settings, we will specify $false.

$doc = ::Load("Documents", $false)

Select-Object –InputObject $doc –Property Name, Count, DefaultSaveFolder, LibraryType

Note that I did not pipe the returned ShellLibrary object ($doc) to the Select-Object cmdlet as I would normally do. Remember that a Library is a collection of objects, so we won't be able to see its properties if we pipe it down. To obtain the properties of individual folders, we will use a pipeline.

$doc | Select-Object Name, Path

Add a folder to the Library

$doc.Add("c:\docs")

Specify the default location to save files(only works if the target directory is already included in the Library)

$doc.DefaultSaveFolder "c:\docs"

Remove a directory from the Library and close the ShellLibrary object

$doc.Remove("c:\docs")

Create a new Library

A library is essentially a .library-ms file. If it is saved in the “$env:appdata\Microsoft\Windows\Libraries” directory, it will be automatically detected and the Library will be displayed in Windows Explorer.

We will create a new “PowerShell” Library and include in it the local script storage folder c:\ps (currently empty).

$ps.Add("c:\ps")

Great. We have created a new library “PowerShell”. Like many readers of this blog, I have many scripts for different occasions: some are for work - located in a folder synchronized via SkyDrive Pro, others for personal use - they are saved in another SkyDrive directory.

Now that I have the PowerShell Library I will be able to display all my scripts with one click. And all I have to do is add the following code to a provisioning script that runs once on each of my new computers.

Add-type -path Microsoft.WindowsAPICodePack.Shell.dll

# For each Library, add SkyDrive and SkyDrive Pro folders (assuming default locations)

::Libraries | % (

$library = ::Load("$($_.Name)", $false)

$library.Add("$($env:userprofile)\Skydrive\$($_.Name)")

$library.Add("$($env:userprofile)\SkydrivePro\$($_.Name)")

$library.Close()

# Create a PowerShell Library and include corresponding folders

$ps = New-Object Microsoft.WindowsAPICodePack.Shell.ShellLibrary –Argument "PowerShell",$true

$ps.Add("$($env:userprofile)\Skydrive\PowerShell")

$ps.Add("$($env:userprofile)\SkydrivePro\PowerShell")

That's all. For more information about the Windows API Code Pack and the ShellLibrary class, see the documentation that is provided with the dll files.

Ed Wilson, Microsoft Scripting Guy

Original: