Tripredacus

On the same question (.net) But surely don't search for javascript or color ...

I don't use multilingual for Windows 7 either. All my OS are single language. So even when I did use French Windows 7, it was French only. For testing, you can test installs in a VM. As far as the Administrator account, I do not recommend enabling that, but if you want to do it, here is the code:

Part of the problem with Google is not their fault at all, but with the kinds of websites that people end up creating. Many search results are aggregates (which is very annoying when trying to do research) and shouldn't really be counted in the results, but you can't select any sort of way to filter those types of sites out. So for example, there are many websites that can mirror some news story, so that news story shows up on multiple sites. Or there are sites that scrape content and create mirrors. For example, there is an aggregate for *some* MSFN content in China (or Russia, I forget) as well as there are ones for MS Social and other forums. Plus there are those "keyword" websites that have nothing to do with what you are searching for!

Ok I am not sure then. Your XML file does not specify a language, so Windows Setup should prompt you to pick a language. It should ask you already... I can't really test, I do not use Windows 8 with multiple languages.

Which of those languages do you want to choose automatically? Here is an example of how to have it pick English as the language. <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SetupUILanguage> <UILanguage>en-</UILanguage> </SetupUILanguage> <UILanguage>en-</UILanguage> <UserLocale>en-</UserLocale> <SystemLocale>en-</SystemLocale> <InputLocale>0409:00000409</InputLocale> </component> Add that setting into the windowsPE pass of your answer file.

Did you happen to reinstall or repair Windows after replacing the board? I have a problem with Office XP where it refuses to open because I had reinstalled Windows. You might need to reinstall Office if this is the case.

Did you install 64bit Office 2013? Also, what OS are you running? I found some things helpful for server OS, look at last post here: http://social.technet.microsoft.com/Forums/en-US/officesetupdeploy/thread/b8e8277c-a2f9-426a-bb3d-3f45bd0a47fc/ Also something about Search 4.0: http://www.neckbeard.ca/r/techsupport/comments/17xmag/windows_installer_starts_with_outlook_2013_on/

I've used some tools before but not had to pay for any. I had the software on my netbook but that is at home, so I don't know which one I actually was able to use. The first thing I'd recommend is to see if your phone manufacturer has their own software. For example, Samsung makes a program called PC Studio. Other ones I found I had tried are BitPim (free) http://www.bitpim.org/ Wondershare MobileGo (trial) http://www.wondershare.com/android-manager/

The key in Specialize should be your MAK/KMS/VLK key. The key you put in Windows PE pass is the install key and is different. You can find some install keys here to use in that pass: http://www.cluberti.com/blog/2009/08/11/default-keys-for-vista-and-windows-7-deployment/

A lot of people that use those tools are having difficulty when using them on Ultrabooks because of the specific partition sizes, extra software. In my opinion, Ultrabook is a failure in this respect.

I'd recommend you do not download hotfixes from any site other than Microsoft, there is no way to know what exactly you had tried to install.

Welcome to the MSFN!

Is this for nLite?

You should maybe contact your network admin to see if you can get a static IP for use in the corporate network, but I suspect that they wouldn't like the idea of you doing this in the first place.

Welcome to the MSFN!

Fixed. I haven't used the program myself. I noticed that on the link you posted, if you click "help" on the left, it goes to their own forum. Maybe the answer is in there.

However... isn't it possible to avoid the Metro mail and remote desktop apps, as one commenter suggests? Or are those services only available, in Win8, as Metro apps? That user's major complaint is that he requires the Microsoft Account in order to install the Touch Remote Desktop app onto the computers. I don't know if he is making images himself or if they are just purchasing PCs with Windows 8 preinstalled on them already.

Windows 8 in the Enterprise are causing headaches for administrators apparently. Some of the functions of Windows 8 such as Mail and others absolutely require that you are logged in using your Live account in order to function. Companies that are now purchasing Windows 8 systems have 2 problems with this: 1. They do not want to administer/manage hundreds of Microsoft accounts for their users 2. They do not want their users to use their personal accounts (if they even have them). Read some frustrated posts here: http://social.technet.microsoft.com/Forums/en-US/w8itproinstall/thread/8124f5da-dd2f-4866-85de-5d369abe1450

The product key in your answer file is the Install Key for Windows 7 Starter.

If this is Windows 8 on a GPT disk, that MSR partition is required. I'm not sure what it does exactly or how the OS would react without it, but it is a requirement for deployment. I wonder if you can add it back in with that unallocated space. http://technet.microsoft.com/en-us/library/hh825686.aspx I should try it out, see how Win8 reacts to that partition suddenly disappearing. edit: will have to wait until monday...

There are multiple problems with your XML I can see off the bat: 1. There is no 64bit version of Windows 7 Starter 2. You cannot activate Windows 7 Starter using that product key in the Specialize pass. For language, presuming your Windows 7 Starter source has French in it (the only downloads I have seen are single language images) you can use this in the windowsPE pass: <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SetupUILanguage> <UILanguage>en-US</UILanguage> </SetupUILanguage> <UILanguage>en-US</UILanguage> <UserLocale>en-US</UserLocale> <SystemLocale>en-US</SystemLocale> <InputLocale>0409:00000409</InputLocale> </component> And this in the oobeSystem pass: <component name="Microsoft-Windows-International-Core" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <UILanguage>en-US</UILanguage> <UserLocale>en-US</UserLocale> <SystemLocale>en-US</SystemLocale> <InputLocale>0409:00000409</InputLocale> </component> You will have to change the locale settings to the codes you need. Look up each of those objects in the WAIK/ADK Unattend help file to find the valid codes.

Not all RAM is the same, and sometimes they are even mislabelled. Plus one of those two could have been bad, did you run Memtest on them?

Welcome to the MSFN!

When it comes to the double backslashes ( \\ ) I seem to recall something from my early days of learning programming. That sometimes you needed to use the backslash as an escape character. I suspect many programs were written with this in mind, and as such would store registry keys this way. So that when that program reads the registry, they can read the keys properly. It was only until later that I learned it is better (but not as nice looking) to handle those extra slashes, quotes, double quotes, etc that can potentially get in the way of parsing a string by using ASCII characters instead. So it could be either an error on the programmer's side that allows these paths to be saved into the registry this way (write the data exactly without stripping out the extra backslash) or potential laziness on the programmer for storing the path this way (so that they do not need to re-convert the path for usage later). Of course all the while not realising that Windows itself may have trouble with these values, especially if (say) some new update or other program attempts to use the data and is not written by the same programmer. The thought doesn't seem too difficult to fix the paths before inserting them into the registry, or reversing the process when reading them: var p = new RegExp(s.replace(/[-[\]{}()*+?.,\\^$|#\s]/g, "\\$&")) https://github.com/viatropos/tower/issues/235 But it could be worse... maybe you can find some paths that use forward slashes instead! myDirname = os.path.normpath("c:/aDirname/") http://pythonconquerstheuniverse.wordpress.com/2008/06/04/gotcha-%E2%80%94-backslashes-in-windows-filenames/ Now I would think the idea of using a backslash as an escape character is a bad idea specifically because it is used in paths. Perhaps this was borrowed from some pre-DOS language? It seems only DOS and Windows based OSes will use a backslash in a path, while Unix and Linux will use the forward slash. The internet is great for programming nowadays, with tons of help on tech and programmer sites, online documentation, etc. However, software isn't always that "new" in a lot of cases, but more like adaptations of older versions. Even drivers suffer this problem where there can still be found some old Windows 95 code in there. This can lead to these kinds of mistakes as well, since not all programmers at that time had access to online documentation, but instead would have to manage their offline manuals. Maybe if you were lucky you remembered to install those TechNet CDs with Visual Studio, or you had those 30lbs of books that came with Visual C. Even then, that's only documentation, you had no real feedback on whether what you were doing was a good idea, and no world-wide resource for finding new ways to do the same thing, or do that thing better. If it worked, that's all that mattered.