Tripredacus

If you mean the updates that you download from the Update Catalog that are just .EXE and not .MSU files, then I don't know. I usually just ignore those. i know it is annoying that you still have updates left to get. One possible way is to grab those updates manually from Audit Mode, then make your image. Be warned, sometimes a conflict may occur and cause the OS not to boot.

Windows OS ISOs are not redistributable. Link to that site has been removed from your post.

The only thing that's really not an incremental improvement would probably be the apparent ability to stack VRAM. Example: You have GTX 980 Ti's in SLI. Normally the machine only sees 6 GB of VRAM because each card is using its own VRAM. However, with DX12 this would become 12 GB of VRAM... apparently. DirectX 12 will add new capabilities that game developers can make use of to make graphics "better" however it is MS who restricts which OS can use DX12. So yes you can potentially get better graphics in Windows 10. The same was true of how Oblivion had better graphics on Vista than it did on XP but that was only because DX10 was only available on Vista. It is a way for MS to force gamers to use the newest OS if they really want to play some new game.

The word "better" is a word of opinion. I'd like to know what made someone say it is "better" (than what) at gaming.

That is referring to the TH1 build that the Insider Previewers use.

Specifying an invalid language shouldn't generate a bugcheck. Is your Windows 10 image natively in that language? The stuff I am seeing is that RTM is en-US and you add a LIP to get other languages. Is that what you did? Also try just using en-US locales and see what happens. I have to say, I have had mixed results with using an unattend file while installing. My first attempt caused a 0x80070017 error (bad media) but install without XML worked fine. Then reinstall with XML worked fine. That was with Win 10 Pro x64. I haven't gotten to test Win 10 Home yet.

It is usually the case that the build at RTM is what ends up being released at GA. There may be some additional updates made available however.

Even if you were to pay actual money, there would be no garauntee that your information had actually been deleted.

The new default wallpaper is pretty cool tho.

I didn't know that was in question.

RegisteredOwner seems to be available in any pass. The documentation doesn't say so you might need to experiment. If it were me, I'd first put it in Specialize. IDK about Mysysprep. One way I know of people using the Serial number from SMBIOS is using a VBScript that runs on first boot. It would be nice if MS made it so someday you could read from SMBIOS and set things in the XML. I'm surprised we haven't seen this yet as many companies would certainly use it.

http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_install/pre-release-product-keys-for-windows-10-insider/97e6cd1f-ee8a-42ea-b76c-46aa4af8e203?auth=1

Yes it will get it from either of those objects if you set it to *. It should be the same for all Win7 OS.

AFAIK, GA and RTM are still different. I don't know about how that GWX thing works into it but I thought it said that those upgrades wouldn't happen until July 28.

10240 is what I am seeing being reported online. Such as here: http://www.theverge.com/2015/7/15/8950481/microsoft-windows-10-rtm-date I haven't seen the DL yet.

Ok this is different than I thought. It sounds like you want to take an existing installed OS and change where it is booted from. Sysprep is not used for this. Regarding the firmware/architecture list, I would consider UEFI/x86 only to be uncommon or even "not rare" overall. I think you could say it is rare in the retail space, however it is more common once you get into embedded, SoC and mobile products. The UEFI/x86/x64 combo is the real rare one.

https://www.thurrott.com/windows/windows-10/4633/on-eve-of-rtm-terry-myerson-speaks-about-windows-10-windows-phones-and-more You'll find out the build number as soon as tomorrow.

Don't DMCA notices typically outline exactly what you are in violation of?

Also more work was put into making the forum, as well as the front page, to be mobile friendly. That way we did not have to rely on a third party app to view the forum. If anyone has any complaints or suggestions regarding how the forum works using just phone/tablet browsers, feel free to post them.

My own personal pattern to create a new image. 1. Deploy OS from DVD to environment* with answer file to put OS in Audit Mode, only have 1 partition. 2. Sysprep /generalize /audit /shutdown. 3. Capture image with DISM (Imagex is technically deprecated and still only has 1 real purpose... exporting images) 4. Add drivers (INF) and updates (MSU) to image with DISM. * regarding your second question, using either a Hyper-V or physical hardware is determined solely on what you have access to and/or find easier. I personally do not use VMs at all for making images and instead only use actual hardware. IMO, using the actual hardware the images are being designed for helps you better understand what settings or quirks those particular systems may have, also then you can provide info to who is going to be using the image if it isn't you. Rule of thumb regarding what not to do. Do not choose a Network Location when prompted with Vista or Win7 images.

http://blogs.windows.com/bloggingwindows/2015/07/09/announcing-windows-10-insider-preview-build-10166/

Always try https as well. I know that on my router (different animal but may be similar) I have it set for SSL only. If I use http to get to the internal page, it will time out. Is it expected to be able to access that page? I know my ISP now makes it so you cannot log into it, unlike years ago when you could.

You are correct. My Win7, 8.1 and Server images were all made on MBR disks and I deploy them both to MBR and GPT disks with no problem. You just need to use different diskpart scripts for each type.

In my experience, Windows is fine on its own. It is only when 2nd or 3rd party software is involved is there a problem. Let's make an example. Said company says to the software maker "hey your software needs to do this in order to be allowed." The software maker goes IDK WHATEVS YOLO LOL. So then the company says to manufactures that all software must comply these rules. But with test (this goes back to prior to Windows 8.0 RTM) manufactures deem software is not in compliance. So manufactures bring this bring this up to software maker and... ZZZZZZZZZZZZZ (aka no response which is happening with Win7 issues too)