Where is gacutil.exe in Windows 10?

Question

I've got Windows 10 Pro 64 bit, Microsoft Visual Studio 2015 and the full Windows 10 SDK package but I'm not able to find gacutil.exe in:

• Microsoft Visual Studio 2015 subdirectories
• Windows 10 SDK subdirectories
• C:\Windows\Microsoft.NET subdirectories
• C:\Windows\System32
• C:\Windows\SysWOW64
• C:\Program Files\Reference Assemblies subdirectories
• C:\Program Files (x86)\Reference Assemblies subdirectories

Don't come tell me it's a duplicate, please. The other answers don't actually answer my question.

Any idea? Thanks in advance!

Solution 1

I had to use the Microsoft Visual Studio 2015 Developer Command Prompt.

Unfortunately, Microsoft KB's are outdated and they usually give the wrong answers.

Go to Start -> Visual Studio 2015 -> Developer Command Prompt for VS2015

Solution 2

If you want find gacutil location then Follow this:

1. Go to Start menu.
2. A-search and find Developer Command Prompt
   or
   B-find and open Visual Studio 201_(2,3,5,7) Folder

3. click Developer Command Prompt for vs201(2,3,5,7)

4. Type and enter:( where gacutil )

5. "Developer Command Prompt" will be return location of gacutil.exe

But if you want cache dll , location of gacutil not necessary, Just run "Developer Command Prompt" and type : gacutil /i "dll_path"

Solution 3

In Windows 10, gacutil.exe is located here:

C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.1 Tools\gacutil.exe

Note that the Framework directory NETFX <version> Tools, can be different; if you don't have 4.6.1 installed, you will have another version installed instead.

To find out where any EXE in your PATH is coming from, you can use the where utility:

Syntax: where <executable.exe>

Comments

[magicandre1981]

I see the exe here: "C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.2 Tools\x64\gacutil.exe"

[Melody]

@magicandre1981 It's not there.

[magicandre1981]

look in the 4.6.1 or 4.6 folder. this depends on which .net SDK you have installed

[marijnz0r]

Why is this not accessible through the regular (or Administrator) PowerShell?

[Paul Rouleau]

Kudos for the correct answer AND showing how you figured it out.

[ephraim]

@marijnz0r cause the SDK's path isn't included in system PATH. browse to the SDK path - and it'll be available.