Tripredacus

I don't trust it. How exactly does that website detect an OS? How much you want to bet the logic is something like: if winver >6.3 then OS="Windows 8"Related:http://reboot.pro/topic/19716-windows-90-discussion/?p=187833 ACTUALLY, it is this: if ((ua.indexOf("Windows NT 6.2") >= 0) || (ua.indexOf("Windows NT 6.3") >= 0)) return "Windows 8";Which is based solely on your browser's user agent, which ISN'T actually reliable since you can change it if you want. Go see what your current user agent is:http://whatsmyuseragent.com/

Don't activate either Windows or Office on the system you are building the image from.

Try this, run a .cmd from FistLogonCommands that runs the following: wmic useraccount where "name='Admin Account'" set PasswordRequired=false It should disable the prompt to set a password.

Run OCCT on it. If that software works for your video card, it can tell you if there are errors with it. In my experience, it will reveal errors within a couple minutes. http://www.ocbase.com/index.php/software/20-occt

Well you just create an account and don't specify a password. <LocalAccounts> <LocalAccount wcm:action="add"> <Group>Administrators</Group> <DisplayName>Admin Account</DisplayName> <Name>Admin Account</Name> </LocalAccount> </LocalAccounts>

One complaint.... Microsoft will not be making Chrome type updates. I'd say it is more like how Firefox pushes out updates. It doesn't do it for you but bugs you every day until you accept the update. Chrome, on the other hand, just updates all by itself without the user knowing. And the strange thing is that I have never seen a BAD update happen. It just seems to work the same, no weird bugs or anything.

Oh an ISO. I should have looked for that. I'm currently trying to use the Windows Update method but it sure is taking its time. (what can I say, this ISO download says it will finish in 33 hours)

Wondering, can you install Windows 8.1 on this PC? I'd expect the same results. There shouldn't be a problem to install this OS on this board, even if not supported.... heck I've installed it on notebooks before. It might help to know the error you are getting. MIGHT. it is also weird that while Windows 8.1 has specific system requirements for CPU, Server 2012 R2 just has a speed. I couldn't find any good list of CPU requirements.

Recovery DVDs are locked to a manufacturer or in some cases a specific model. Are you asking how to say (for example) take a Dell Recovery DVD and make an OS you can use on any make and model computer?

I'm not sure (I can try tomorrow) but if it lets you do that... It requires a reboot and then you would have no video. Windows may consider that one of those boot-critical devices and deny you the option if it is the only video adapter in the system.

CPU speed has no bearing on whether or not Hyper-V is supported. Here's the sheet for yours: http://ark.intel.com/products/33910/Intel-Core2-Duo-Processor-E8400-6M-Cache-3_00-GHz-1333-MHz-FSB?q=e8400#@specifications And it seems fine. It sounds like you are getting an error booting into WinPE from DVD or PXE. I would start with that and forget about the in-place upgrade for now. Try doing the install with a lower amount of RAM.

Its a fake, but funny.

A few things I found, to lighten the mood. Obviously. But then there's the Windows OS vs Star Trek movie rating trend. But as pointed out, if this trend were to continue, Windows 10 is going to be "crap" as the "good" Windows 9 was shelved. Lastly, large image in a spoiler... source: http://knowyourmeme.com/memes/subcultures/windows

Ah wait, I am confused as to where you are getting this black screen error. Is it while booting off the DVD/PXE or during the second phase installation? Try having only the disk/volume you want the OS installed to connected. Disconnect any other drives including any USB or card-reader types. Windows Setup sometimes will write boot files on another volume, causing the second phase of installation (the part that boots off the HDD) generate a BCD error.

Well my Google Chrome is currently up to version 37... Microsoft can use this method if they want, but they'll have to try something new once it starts getting close to version 95.

Was Windows 9 so bad they decided to skip it altogether?

Its funny, that guy isn't even using that "computer" he is standing in front of.

I totally suggest this too. The information is present in Post #2 of this thread.

Ok I went back to read the first post. You refer to your problem with "the" Windows 7 Pro x64 image. The incompatibility I outlined will exist in other Windows 7 x64 images as well. Is this not the case or did you not add the same drivers to all your images? Did you disable driver signing? Do you keep track of what drivers you are adding for what reason or did you just add a bunch all at once? I qualify a new system and verify it works once at a time. When I ran into this USB problem, I was able to determine the cause because I knew what drivers I had added in between the working and non-working deployments. I also keep backups of images in case such a thing happens, so I can roll back to a working set while troubleshooting the issue. If a worst case scenario occurs, I would be left with having to rebuild the image from scratch OR creating a new version for affected devices. I've had to do that once already during the Windows 7 SP1 lifecycle and it wasn't fun. Intel USB3 drivers have 2 or 3 INFs. Removing the iusb3xhc ones should be enough, however they also have a hub INF called iusb3hub. If you want to eliminate all USB related drivers, create a copy of the problem image, then using the DISM /GET-DRIVERS output (not the /ALL switch) remove all drivers shown as being from Intel and USB type. Redeploy the test image and see what happens.

Well those two oem names I posted were a guess. You'll have to determine it for yourself. If you find any INF with the REV_05, remove it from the image with DISM. And as I said before, it is a known issue that the USB drivers I am talking about will cause this BSOD, but I am not saying it is what is causing your BSOD. I didn't find anything in the setupact.log. The log is incomplete, as evidenced that the bugcheck occurred and it didn't seem to write anything to a log about it.

How is the compatibility with Office 2003 and Windows 7? Bellzemos, will you be getting 32bit or 64bit?

Ok some of these you'll have to inspect yourself. I see you had taken drivers from another OS, so their original filenames are not preserved. If I were to guess, I'd say look at the published names oem148 and 149 with version 2.5.1.28. I don't keep old driver versions around, but the offending version I have is 2.5.0.19. You'll need to search the drivers folder by mounting the image. Search for containing text. The USB driver issue is with these hardware IDs: VEN_8086&DEV_8C31 VEN_8086&DEV_9C31 The older drivers will have a REV_00 to REV_04 in the HwID list. The new drivers will have those plus a REV_05. Remove any drivers with the REV_05. Original filename is iusb3xhc.inf Now, I'd like to point out that it isn't confirmed that your problem is the USB driver issue. You might have it set up like this, and resolving it may not solve your error.

The official word (no pun intended) You can buy Windows 7 OEM System Builder Kit from major online retailers like Amazon or Newegg, so probably other online shops too. That media isn't licensed/intended for personal use. The Office license doesn't permit being moved from the original computer. http://answers.microsoft.com/en-us/office/forum/office_2003-office_install/office-2003-oem-reinstall/69fe900c-1340-48d2-b11c-cedefcdd8a60 Microsoft wants you to buy new Office and buy the more expensive Windows 7.

The results you post have the appearance of being from a stock WIM and not a modified one. You didn't inject those printer drivers either. Verify you are checking against the correct image and (if relevant) index. Also check for the setupact.log in C:\windows\panther of the PC that can't boot.

Hmm you used the /all switch huh. Do you get different results without it? When using /all you see the MS ones, which aren't likely to be the problem. Your DISM output shows no third-party drivers, which have a published name starting with oem. Also, bugcheck 0x7E on first boot after deployment can be caused by having REV_05 and a lower REV (3 or 4) drivers for Intel USB 3.0 controllers in the same image. Reference (if applicable to you) http://social.technet.microsoft.com/Forums/windows/en-US/9af3ae94-bcc9-4d26-a31b-67e49df2f401/bsod-on-first-boot-after-deployment-no-minidump?forum=w7itproinstall http://social.technet.microsoft.com/Forums/windowsserver/en-US/bf5d402d-edd0-4556-ab69-7f831b98ae3c/server-2008-r2-wds-intel-series-8-usb-issue?forum=winserversetup