Update-Gac.ps1

MSDN Blog Postings » Update-Gac.ps1

MSDN Blog Postings » Update-Gac.ps1 — Thu, 08 Nov 2007 20:57:10 GMT

PingBack from http://msdnrss.thecoderblogs.com/2007/11/08/update-gacps1/

re: Update-Gac.ps1

Chris Lieb — Thu, 08 Nov 2007 23:23:03 GMT

I noticed that when this ran that it was unable to compile assemblies that were loaded by PSCX (PowerShell Community Extensions). How would you modify this script to handle assemblies that belong to other snap-ins?

re: Update-Gac.ps1

Heath Stewart — Fri, 09 Nov 2007 19:35:43 GMT

Technically you're not updating the GAC. You're updating the Native Image Cache, or NIC. These are actually both foldered directly under %WINDIR%\assembly.

re: Update-Gac.ps1

Anonymous — Fri, 23 Nov 2007 17:47:13 GMT

This script has an oversight and does not locate ngen correctly. It does not work properly since I have a _folder_ called "ngen.exe" located here: C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\Bind Logs\ngen.exe\

re: Update-Gac.ps1

Anonymous — Fri, 23 Nov 2007 18:38:24 GMT

Adding a filter for item length works better since you filter only files that way, and don't accidentally include bind log directories that are named ngen.exe:

set-alias ngen @(dir -recurse (join-path ${env:\windir} "Microsoft.NET\Framework\") ngen.exe | where {$_.length -gt 0} | sort -descending lastwritetime)[0].fullname

[appdomain]::currentdomain.getassemblies() | %{ngen $_.location}

re: Update-Gac.ps1

PowerShellTeam — Sun, 25 Nov 2007 19:27:29 GMT

> since I have a _folder_ called "ngen.exe"

I'm dying to know: Why do you have a folder with an EXE name?

Jeffrey Snover [MSFT]

Windows Management Partner Architect

Visit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShell

Visit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx

re: Update-Gac.ps1

June Blender — Sat, 14 Jun 2008 03:50:07 GMT

On Vista, you need to start Windows PowerShell with the "Run as administrator" option to run this successfully.

When it fails, the output contains a bunch of "access denied" messages.

re: Update-Gac.ps1

JaredReisinger — Fri, 11 Jul 2008 02:56:27 GMT

This is a great bit of script. I've shared this out with several people on my team, and it's resolved all of the "PowerShell is slow to start" comments.

Can you say anything about whether this will still be useful/needed on PowerShell v2? I understand wanting the installation to be responsive, but I'd rather wait an extra minute or two during the installation if it means that PowerShell starts more quickly the first time.

PowerShell speed-up script

Abstract Semantics — Fri, 11 Jul 2008 03:22:04 GMT

Jeffrey Snover posted (back in November of 2007) a script that solves the "PowerShell starts slowly"

re: Update-Gac.ps1

PowerShellTeam — Fri, 11 Jul 2008 05:22:11 GMT

> Can you say anything about whether this will still be useful/needed on PowerShell v2?

We will have the problem fixed in V2.

Jeffrey Snover [MSFT]

Windows Management Partner Architect

Visit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShell

Visit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx

Speeding Up PowerShell Startup

Windows PowerShell — Fri, 11 Jul 2008 15:16:03 GMT

I talked about this before but a number of people have missed it so here it is under a better title.

re: Update-Gac.ps1

Bruce — Fri, 11 Jul 2008 19:14:23 GMT

WOW - no real numbers but significant reduction in startup time

Fix PowerShell startup times with a PowerShell script

Rod Trent at myITforum.com — Fri, 11 Jul 2008 22:46:44 GMT

Annoyed with how long PowerShell takes to startup?  Run this script… http://blogs.msdn.com/powershell

re: Update-Gac.ps1

Mike Schinkel — Sat, 12 Jul 2008 06:55:13 GMT

OMG!

Slow startup times were actually my (only) ONE major complaint about PowerShell, though I assumed there was nothing you could do about it so I hadn't complained about it.

WAY COOL! THANKS!

re: Update-Gac.ps1

Shaun Cassells — Mon, 14 Jul 2008 17:28:03 GMT

Great Script,

Be aware, you need administrator access on the workstation to complete the execution.

re: Update-Gac.ps1

DM — Tue, 15 Jul 2008 03:14:53 GMT

Don't forget that on x64 systems, you need to use "Microsoft.NET\Framework64" instead.

re: Update-Gac.ps1

Jay Bazuzi — Fri, 18 Jul 2008 20:30:30 GMT

Consider passing "/nologo" to ngen.exe, to reduce noise.

re: Update-Gac.ps1

robby — Mon, 21 Jul 2008 09:02:36 GMT

Great info (as always)!

As I'm not a .NET-guy, where can I find some backgroud info on GAC, ...

Speeding Up PowerShell Startup

HyperVoria — Wed, 23 Jul 2008 10:33:29 GMT

Jeffrey Snover [MSFT]: In V1, we had a problem which caused our assemblies to not get ngen'ed during

re: Update-Gac.ps1

Justin — Thu, 24 Jul 2008 02:10:28 GMT

I made a couple of tweeks to add detection of x86 and AMD64:

Set-Alias ngen @(

$ngen_path = Join-Path ${env:\windir} "Microsoft.NET\Framework"

if(${env:PROCESSOR_ARCHITECTURE} -eq "AMD64"){

$ngen_path = Join-Path ${env:\windir} "Microsoft.NET\Framework64"

}

dir $ngen_path ngen.exe -recurse | where {$_.length -gt 0} | sort -descending lastwritetime

)[0].fullName

[appdomain]::currentdomain.getassemblies() | %{ngen /nologo $_.location}

re: Update-Gac.ps1

Fred — Thu, 24 Jul 2008 05:26:43 GMT

Can you use this to speed up Exchange Management Shell as well? As this always take a long time to load up!

re: Update-Gac.ps1

Justin — Thu, 24 Jul 2008 19:09:27 GMT

Yes it does speed up the exchange managment shell. it is still a little slow, but a major improvement.

re: Update-Gac.ps1

EDF — Fri, 25 Jul 2008 00:22:48 GMT

FANTASTIC! Thank you!

I tested on XPsp2 and Vista Ultimate sp1 - both with great success. The above comments helped too.

More on Update-GAC (speeding up PowerShell startup)

Michael's meanderings... — Fri, 25 Jul 2008 22:10:15 GMT

Jeffrey Snover of Microsoft, PowerShell dude extraordinaire, recently reminded us of a way to Speed Up

PowerShell Startup

Richard Siddaway's Blog — Sun, 27 Jul 2008 03:24:39 GMT

If you think your PowerShell startup is slow, or even if you think it is OK, follow the instructions

re: Update-Gac.ps1

Glen Martin — Fri, 01 Aug 2008 23:34:40 GMT

Am I correct in assuming that this script, in order to retain its benefits, would need to be re-run after any update or patch to Exchange or the .NET Framework?

re: Update-Gac.ps1

japanese — Sat, 09 Aug 2008 08:27:41 GMT

re: Update-Gac.ps1

Brian Reiter — Wed, 13 Aug 2008 18:44:26 GMT

Error for System.Data.dll on x64 PowerShell.

For some reason ngen always fails to comile a native image of System.Data.dll on PowerShell x64. Here's the relevant message.

Microsoft (R) CLR Native Image Generator - Version 2.0.50727.3053

Installing assembly C:\Windows\assembly\GAC_64\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll

Failed to find dependencies of image C:\Windows\assembly\GAC_64\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll be

cause this image or one of its dependencies is not a valid Win32 application.

Compiling assembly C:\Windows\assembly\GAC_64\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll ...

Error compiling C:\Windows\assembly\GAC_64\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll: An attempt was made to

load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)

Uninstalling assembly C:\Windows\assembly\GAC_64\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll because of an err

or during compilation.

re: Update-Gac.ps1

Josh Einstein — Fri, 22 Aug 2008 22:48:41 GMT

There's a pretty easy way to get the framework path. I noticed some commenters trying to make it find the right version of ngen or what not...

$FrameworkPath = [System.IO.Path]::GetDirectoryName([Object].Assembly.Location)

$NgenPath = [System.IO.Path]::Combine($FrameworkPath, "ngen.exe")

re: Update-Gac.ps1

Yuvi — Tue, 26 Aug 2008 16:17:42 GMT

@Brian - Making Microsoft.NET\Framework into Microsoft.NET\Framework64 as DM said.

re: Update-Gac.ps1

Kirill Osenkov — Tue, 02 Sep 2008 11:03:45 GMT

One can also determine the .NET framework install path using RuntimeEnvironment.GetRuntimeDirectory()

http://blogs.msdn.com/kirillosenkov/archive/2008/05/07/how-to-determine-the-net-installation-directory-and-clr-version.aspx

re: Update-Gac.ps1

Feras Mustafa — Sun, 28 Sep 2008 11:15:42 GMT

I tried this Script and it does not do any thing to speed the start-up of poweshell console for Exchange 2007 installed on a Windows Server 2008!!! Any idea on how to fix this??

Thanks.

Speed up PowerShell

Howard van Rooijen's Blog — Thu, 30 Oct 2008 20:06:22 GMT

Jeffrey Snover just dropped this little gem into the " PowerShell: Creating Manageable Web Services "

Speed up Powershell V2?

Josh Smith — Sat, 01 Nov 2008 01:18:16 GMT

I ran the script in V2, still takes on the order of 15-20 seconds to get to PS when issuing powershell.exe from cmd. I'm worried about the scripting speed. I need to poll 300 machines repeatedly for very specific info. It's starting to sound like I need to use a binary or maybe wscript

re: Update-Gac.ps1

PowerShellTeam — Sat, 01 Nov 2008 02:03:24 GMT

@Josh

That doesn't sound right - we should be able to meet your needs. Can you do the following and post it:

1..10 | %{Measure-Command {powershell exit}}|ft totalseconds

gwmi win32_processor |fl name,NumberOfCores,MaxClockSpeed,L2CacheSize

gwmi Win32_PhysicalMemory |ft tag,speed,{$_.capacity/1mb} -auto

Thanks!

jps

re: Update-Gac.ps1

Jeff — Thu, 13 Nov 2008 23:07:56 GMT

Even after running this script my powershell takes > 20 seconds to start (either from shortcut or by typing powershell from cmd). Starting it from within powershell itself is fast.

Here is the output from the commands Josh suggested:

PS C:\Documents and Settings\jdease> 1..10 | %{Measure-Command {powershell exit}}|ft totalseconds

TotalSeconds

------------

0.6983097

0.6771509

0.7174827

0.6861359

0.6862929

0.7018789

0.6871349

0.6774461

0.6860443

0.6863205

PS C:\Documents and Settings\jdease> gwmi win32_processor |fl name,NumberOfCores,MaxClockSpeed,L2CacheSize

name : Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz

NumberOfCores : 2

MaxClockSpeed : 2128

L2CacheSize : 2048

PS C:\Documents and Settings\jdease> gwmi Win32_PhysicalMemory |ft tag,speed,{$_.capacity/1mb} -auto

tag speed $_.capacity/1mb

--- ----- ---------------

Physical Memory 0 667 1024

Physical Memory 2 667 1024

re: Update-Gac.ps1

radhat — Thu, 30 Apr 2009 01:10:10 GMT

Mine went to .5 secs

don't know what it was before, but this put some pep in it's step (both ways)

re: Update-Gac.ps1

Jason — Mon, 23 Nov 2009 22:36:58 GMT

Sorry to open an old topic, but I have a single server, having real problems opening powershell. I have run the script attached to this thread, and it does throw errors trying to load the pscx.dll:

Installing assembly C:\Program Files (x86)\PowerShell Community Extensions\Pscx.dll

Failed to load dependency Pscx.Core of assembly Pscx, Version=1.1.1.0, Culture=neutral, PublicKeyToken=null because of t

he following error : The system cannot find the file specified. (Exception from HRESULT: 0x80070002)

The script did not improve loading times (3+ seconds). here is oupt from JPS's information script (put noprofile in, as my profile adds some overhead):

PS C:\> 1..10 | %{Measure-Command {powershell -noprofile exit}}|ft totalseconds

TotalSeconds

------------

3.8922882

3.2950101

3.4424849

3.4869485

3.448749

3.2428333

3.2916778

3.179595

3.5320035

3.352735

PS C:\> gwmi win32_processor |fl name,NumberOfCores,MaxClockSpeed,L2CacheSize

name : Intel(R) Xeon(R) CPU E5320 @ 1.86GHz

MaxClockSpeed : 1863

L2CacheSize : 0

name : Intel(R) Xeon(R) CPU E5320 @ 1.86GHz

MaxClockSpeed : 1863

L2CacheSize : 0

name : Intel(R) Xeon(R) CPU E5320 @ 1.86GHz

MaxClockSpeed : 1863

L2CacheSize : 0

name : Intel(R) Xeon(R) CPU E5320 @ 1.86GHz

MaxClockSpeed : 1863

L2CacheSize : 0

PS C:\> gwmi Win32_PhysicalMemory |ft tag,speed,{$_.capacity/1mb} -auto

tag speed $_.capacity/1mb

--- ----- ---------------

Physical Memory 0 4096

I tried running the script inside of powershell, and launched from a script. I tried with and without PSCX installed. I made sure to point to the correct framework directory (x64). I cant get powershell to load in under 3 seconds.

Thanks,

Jason

re: Update-Gac.ps1

Jason — Mon, 30 Nov 2009 18:26:02 GMT

I finally tracked down the reason for my problems. I am using signed scripts, and have set up an internal certificate server for the code signing cert. The server does not have the required access to that server. The code signing cert I created has references to the CRL as:

URL=http://<certserver>/certenroll/<caname>.crl.

I needed to add permissions to that crl for everyone (off domain), and add firewall rules on port 80.

The server was not able to cache the CRL.