Generic Key To Install Windows 10 RTM
Janet Denzel
I'd like the ability to download and install a generic client installer, that asks me for information during the install, such as name, organization and location etc.. Often when I'm doing a multiple computer deployment, I have to download a bunch of the same installer file with the different information and then make sure I install the right exe on the right computer. If i had a generic one, i could run it, punch in the info on the spot and only need a single installer. Would be super helpful. I doubt this would be very difficult, I'm guessing somewhere in the exe is a configuration file that has this information programmed when its downloaded from the site.
Make this information scriptable would be helpful too. For example the ability to add Organization to a generic installer via a script/command would be significantly useful. Especially with the need to code sign custom branded installers. This is not a process that is helpful to repeat over and over.
I can open the windows installer in Winrar and it shows a bunch of files, including a .exe.config file however when i try to extract them, I get an archive corrupt error. There are files created in appdata/local/temp when you run the base exe but its just a setup.msi file.
In the setup.msi that shows up in windows temp, can also be opened by winrar, and the same files, plus some more show up including an app.config file and some client.resources files. But again, corrupt archive when trying to extract.
I think I might have found it - if it's where I think it is it's surrounded by a long has making it not really editable but what I am thinking is to create a generic installer with a very unique Organization name then running a sed command after the install to swap the name to the Organization I want - we'll see what that does
That's not a bad idea actually, just make the company "unbranded" or something like that and same with the "name" and "location" if you use that, then just edit it after the fact. However what happens if you install the client on more than one computer before you edit, do they just show up as duplicates? Might be hard to tell if you're doing a lot and dont want to update on your instance until after you're done. Although you could leave the "use pc name" instead of custom name and then if you have names documented then you could do it that way. Really good work around actually until they come up with something.
7-zip can open both the original installer and the setup.msi however neither ".config" files have any specific info in them related to customer, instance, name etc... just some general options. However when you run the base .exe, a folder in temp files appears but there's no files in it...or there are files being created in there but they are run and deleted so fast, you cant see them. WOuld need to be able to step into with the installer to see if there are files there.
It would also be nice to be able to install via command line and use switches for settings such as which group the device belongs to. This would be handy when deploying via RMM. example. c:\connectwise.exe /group "Company A"
I've had to reset my Surface Pro 7 (SP7) because the touchscreen and windows hello kept having issues. I went to reset my copy of Windows 11 Pro through using Windows Settings but during the reset it got stuck in a loop and wouldn't complete the reset.
I then did a hard reset (I couldn't get into the computer as it was looping that there was a problem and trying to install again) to bypass this loop. By hard resetting I was finally about to reinstall Windows 11.
Windows 11 Home ended up installed I've tried using the store (which prompted me to install Pro license) it bombed with an error. So, I've tried this method, and the same thing. It bombs showing installing the Pro license and then I go into reboot where it states I'm updating but then it bombs and says it's going to roll back (which is Windows 11 Home).
I can't seem to be able to install the Pro license. I have noticed that every time I try to install the pro license the Virus protection pops up after the above happens and states that the msi file is a threat and removes it.
@angelobio This worked for me also with an additional step. I also needed to go into Check for Updates and apply all of them -- especially the 2022-08 cumulative updates for arm64-based processors. After that, I finally activated as well. Thanks so much!
While my original answer should still work, I've updated it with a slightly more optimal version based on the directions on the usbipd-win Wiki. Note that these instructions should also work under Ubuntu 20.04, as well as most Debian-lineage distributions:
This will install the usbip client from the latest Ubuntu kernel package. This client (/usr/lib/linux-tools-/usbip) is compatible with the WSL2 kernel, but the linux-tools-common package includes a stub (/usr/bin/usbip) that tries to find the tools in a directory corresponding to the installed kernel.
Keep in mind that, no matter what, your WSL2 kernel is not going to match any kernel version in the Ubuntu repositories. For this reason, you'll need to create a symlink (via update-alternatives) with a higher priority than the linux-tools-common package's /usr/bin/usbip.
These tools need to match your systems kernel version. You can see your current version by running uname -r. The Microsoft docs link in the question alludes to this in the Prerequisites note by saying that you need to run uname -a, which shows multiple pieces of system information, to find your kernel version.
The linux-tools-generic package is linked to the latest kernel version. If you're not looking for a package matching a specific kernel version you can just install that package. I haven't tested yet whether a kernel update will cause the linux-tools-generic package to update to the latest version.
Just today my WSL kernel updated to 5.15.79.1-microsoft-standard-WSL2 but the latest available package in Ubuntu is still linux-tools-5.15.79.1-microsoft-standard-WSL2. I'll probably try building the tools from source next to be able to try out USB/IP under WSL.
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
When you configure Cubase you should be able to select from 3 options:
WDM driver (windows driver model driver)
Generic asio (speudo asio wrapper from Steinberg to use WDM driver)
Vendor ASIO - you should see something called LYNX ASIO Driver, this is the one you want.
There is a directory named Asio in your C:\Program Files\Steinberg directory. Just make a back-up of this directory (very important - I will explain later why), and simply remove this directory from the given location.
Now restart windows, and you will notice Sonar no longer uses that generic ASIO driver. It makes no difference for Cubase, because you should use the device ASIO driver in stead of a generic driver anyway. Problem solved.
Lynx support suggested that a list has somehow been modified without updating the indexes or some such thing, thereby shifting all of the names. Consequently, the backend is still working - my Lynx device is still producing audio - but Device Manager (and who knows what else) is out of whack. Moving forward without correction, things would only get more confused or broken.
When you say, just make a back-up of this directory, are you referring to simply moving that directory to somewhere else on the computer (as in cut and paste)? And in that case, is there no need to mess with the Windows Registry?
The generic ASIO driver comes in play when there are no real ASIO driver ( onboard audio?), it wraps the wdm to use as ASIO.
Asio4all is another way of doing the same ( never use these hacks for any serious work)
The Generic Low Latency ASIO Driver has well-documented problems with other applications (e.g., Sonar). As such, it might not be common knowledge in these forums, but a general Google search will reveal more, should anyone need it.
Anyway, deleting the Steinberg Generic ASIO driver is not enough, but, going into the Regedit program as described took care of my problem with WL - and for that I am very grateful to you and your post!! Thank you!!
bcf7231420