Windows Server 2008 R2 Activator Loader
Mack Mosely
Ok..i dont get it...I actually performed the exact same method and it is working for me.... i didnt use the key while install or after install..i just used it for converting the eval to full version and then activated using the activator.
Good Morning
To : chinchin85
hello sir
as I saw your response regarding a person having trouble i liked to write a message to you , as i am having some problems with my computer , I currently have windows 10 pro and i have not activated it yet as i dont have a product key but i tried to activate it through cmd and it activated but it is showing activated but i cant personalize my comp. and it is showing activate windows .
so if you can help me then its your great pleasure
Thank You
wating for your response
Also this is a Windows Server thread so Win 10 questions might not be allowed here so refrain from asking question in an incorrect thread, else thread moderators could remove your question altogether.
@chinchin85 It's not that questions about other products aren't allowed as much as we want to make sure that your questions get routed to the right teams, so if we see a post that is for a different product, we attempt to move it to the right forum to be addressed. Thanks for your feedback.
Thanks for the reply. My questions were based on Win 11 22H2 Preview branch being same as Server 2022 preview i.e 22463, hence the query regarding the release timeline (possibly of a Windows Server 2022 R2 or so...). But as you said, LTSC releases would happen after a gap of 2-3 years so that clarifies my queries. Thanks again
Activation contexts are data structures in memory containing information that the system can use to redirect an application to load a particular DLL version, COM object instance, or custom window version. One section of the activation context may contain DLL redirection information which is used by the DLL loader; another section may contain COM server information. The activation context functions use, create, activate, and deactivate activation contexts. The activation functions can redirect the binding of an application to version-named objects that specify particular DLL versions, window classes, COM servers, type libraries, and interfaces. For more information about the activation context functions and structures, see the Activation Context Reference.
Beginning with Windows XP, activation context functions enable Windows to use information in manifests to create version-named objects. If an application creates a process by calling CreateProcess, Windows checks for the existence of an application manifest. If a manifest exists, Windows uses the information in the manifest to populate the activation context. Because manifests describe an application's dependence on side-by-side assembly versions, objects specified without versions in the manifest are mapped to version-named objects. For example, the manifest may describe DLLs, files, window classes, COM servers, type libraries, and interfaces.
When a global object is created within the activation context, the system automatically gives the object a version-specific name by consulting the manifest. When the application executes and requests a named object, it gets the version-named object. This enables multiple versions of a code module to run on the system at the same time without interfering with each other. For example, Windows Shell uses a manifest to describe a dependence on version 6.0 of COMCTL32 and to create versions of window classes.
If an application creates a resource by calling CreateWindow, the process specifies a class name to that function. The call to GetCurrentActCtx gets the current activation context and checks to see if a mapping exists for the given class name. If a mapping exists, it will use that version of the calling process to resolve the mapping and provide the version-specific class name. Windows creates a window with the window procedure, styles, and other attributes associated with that class name and version.
The activation context is managed by the system in most cases. Application developers and assembly providers do not commonly need to make calls to the stack. Applications can manage an activation context by directly calling the activation context. For more information, see Using the Activation Context API.
Goal:From a .NET 4.7 console app, using reflection with Assembly.GetType(), I am trying extract the Type of a netstandard 2.0 class from Assembly X. Then I want to create an instance of this Type with Activator.CreateInstance().
What I am trying to do:However, this assembly X has a dependency to netstandard 2.0. To be able to get the Type, netstandard dependency has to be loaded into the AppDomain. That's why when the AppDomain is requesting the netstandard assembly through the AssemblyResolve event, I simply load the dll like this :
What I know:I know that they want us to load the DLL with Assembly.ReflectionOnlyLoadFrom. But doing that will prevent me from instanciate the type with Activator.CreateInstance(). See Microsoft official post
Question:Does anyone would know if there is a proper way to load that dll without error, or maybe if this is a bug, or else? Or why this kind of dll is not able to load for execution?
The netstandard.dll you are trying to load is a reference assembly that cannot be loaded for runtime on .NET Framework as pointed out by others. However if you need to resolve that dependency you will need to runtime version that maps to the framework you are trying to run on.
For .NET Standard support we are including them as part of the msbuild extensions that ship with VS so you will want to get the version of netstandard.dll from there. Depending on which version of VS2017 you have installed it should be somewhere like C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\Microsoft.NET.Build.Extensions\net461\lib\netstandard.dll or from the .NET Core 2.0 SDK you can find it C:\Program Files\dotnet\sdk\2.0.0\Microsoft\Microsoft.NET.Build.Extensions\net461\lib\netstandard.dll
For me, the problem was that my .NET Framework project (which references both .NET Framework and .NET Standard libraries) was built with .NET Framework 4.7.2 and the system where I was deploying and running it did not have 4.7.2 installed.
Deploying a very small Console project with the same basic structure and references and executing that in a Command window finally revealed the correct error, in a pop-up, that .NET Framework 4.7.2 was missing.
For me solved doing the following:1 - Installed latest .Net Framework on server.2 - Updated windows server and my local machine. 3 - Went to Manage Nuget Package and updated all references on the update tab.
In case if IBM Message Queue references are used in the project solution, this exception indicates that the DLL used for refering MQ classes are incompatible with the host(server) .NET version installed.
Windows Server running the Volume Activation Services role can act as a KMS (Key Management Service) server, allowing you to activate computers with volume editions of the Windows Server and Windows 10/11 operating systems in a corporate network. In this article, we will show you how to install and configure KMS Host on Windows Server 2022, 2019, or 2016, and how to use it to activate Windows on client computers. (adsbygoogle = window.adsbygoogle []).push();
To deploy your own KMS server, you must install the Volume Activation Services role on any of the hosts running Windows Server 2022, 2019, or 2016. If you already have a KMS host on Windows Server 2016 or Windows Server 2019, you can use this existing server (in this case, this section can be skipped). Clients running newer Windows Server 2022 and Windows 11 can be activated using such a KMS host.
A special GVLK (Generic Volume License) key must be installed on Windows computers to activate them against your KMS server. GVLK keys are public keys that indicate that this computer will be activated on the KMS server. Visit the Microsoft website for a complete list of client GVLK keys for all supported versions of Windows ( -us/windows-server/get-started/kms-client-activation-keys).
In this case, it is Windows 10 Pro. Find and copy the GVLK key for this OS version from the link above. In our example, the KMS Client Product Key for Windows 10 Pro is W269N-WFGWX-YVC9B-4J6C9-T83GX.
In this case, the VOLUME_KMSCLIENT channel and License status: Licensed values indicate that the Windows OS on this computer is activated through the KMS server. The client is activated for 180 days and is automatically renewed every 7 days (if the KMS server can be reached).
I am doing my nut in with the Windows Server 2019 CSVLK and GVLKs. The latest version of VAMT from ADK says they are unsupported. My KMS Host is Server 2019 and updated to February 2022 CU. It happily accepts the CSVLKs and GVLKs for all other Server OS, even 2022.
OUR KMS host is W2012 R2 server and it has the patch KB3173424 and the latest security update KB4512488. I installed the Windows Srv 2019 DataCtr/Std KMS key on this host machine and it was successful. Now on my client which is a server 2019 std when I try to activate I get an error stating 0XC004F074 No KMS service could be contacted. This client can actually communicate to the host like I can telnet to KMS Host on port 1688 and then I have manually set the KMS host by using the slmgr.vbs /skms hostserver:1688 cmd.
The first of all, check the time on the kms host and client (the time of the server and client should not be so different, otherwise actication requests may be rejected).
Have you activated your KMS host with a new KMS host key?
What version (build) of Windows are you trying to activate?
KMS keys are no longer pre-assigned to Open agreements as use of MAK (Multiple Activation Key) keys is the preferred method for activation.
KSM keys can be assigned, by exception, to Open customers who meet the minimum KMS activation threshold for Windows Server, OS, and Office. To request such an exception, please submit a Web Form request to VLSC Support.