Tripredacus

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)

Are there Vegas odds on this?

ST Microelectronics Free Fall Sensor or ST Micro Accelerometer. Driver here: http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=K3TWC You can extract the initial EXE and then use install.exe with this (from the readme.txt) /v"EXTRACTDRIVERS=<path>"Extracts the drivers contained in the installer package to the specified folder.It extracts to 3 OS folders. In the Win7 folder and you'll find st_accel.inf to use.

Yes. During OOBE you choose not to use Express Settings.

4. The WinPE is created using the WAIK for Windows 7 or you can use the ADK for Windows 8.1. For Vista/7 PEs you can refer to this: http://www.msfn.org/board/topic/144914-guide-creating-wim-images-of-windows-for-system-deployment-using-pe/ However Win8 PE is fairly similar. 6,8. You can run install programs using RunSynchronous or FirstLogonCommands in the XML file. 7. You can integrate Hotfixes, Windows Updates and Drivers (INF based) into you install.wim using DISM. See this sticky http://www.msfn.org/board/topic/146986-windows-7-deployment-documentation/ Also, you might want to look into MDT instead of having to do everything manually. MDT works with either a PXE boot environment, or if you don't have that you can create bootable media with it instead.

On a side note (and apparently now the branding is public) Microsoft has officially grabbed onto the Internet of Things and will be using it as part of a new Embedded product line. You can see their use of the term here: https://www.microsoft.com/windowsembedded/en-us/community-blog.aspx

http://www.msfn.org/board/topic/174037-broken-app-in-start-menu-after-upgrade-to-1015810159/

Perhaps. See Zigzag's comment here: https://social.technet.microsoft.com/Forums/en-US/baa36140-526f-4b01-aa60-79a57525a964/is-there-a-new-windows-10-adk-version-i-can-only-find-adk-with-build-10075-released-along-with?forum=WinPreview2014Setup

I'm reading that there are Windows 10 TP ADKs being released with each new Build. Are there any differences in these new ADK versions concerning the files your tool downloads?

Two things. First it is hard to tell exactly from the first post but it is worded as if you are connecting the SATA drive after the computer is turned on. Is this true or do you connect it prior to turning on the PC? Second is that you can get an internal drive enclosure that has the ability to remove or undock a SATA drive. I know this would be more of a manual process but it could work for you. The one I have is this, although there are certainly other ones out there: http://www.istarusa.com/istarusa/products.php?model=T-7-SA If I don't want the drive detected, I just unlock it. The lock mechanism works in such a way that it will push the internal enclosure outwards from the bay itself, which will disconnect the drive from the SATA connection. You don't even need to take the drive out.

Does it get detected by Windows and if so what is the Hardware ID?

No, Four weeks from GA. On many other forums I'm on, I'm seeing a lot of optimism over Windows 10.

Yes I suspected that the time sync would fix it. Good thing tho... What timing!

Yeah, things like this end up in "white whale" category. Unless you want to drive yourself insane, I wouldn't actively search for them and instead focus on something else. In my own collecting ways, I always find I cannot ever locate the thing I'm looking for until I start looking for something else.