Tripredacus

I think it really depends on usage. I have never run out of hard drive space on OS volume with actual programs and I typically use 80GB disks. My current PC has an SSD, I think 160GB but the only game installed on it is Minecraft. Data understandable to put on another volume. Programs are usually not as forgiving. As an example, if you were to install Office on a different volume, and for whatever reason reinstall/change your OS, that Office installation won't be usable. But it depends on which programs they are for sure.

So apparently one change I found from 1511 (and earlier) to 1607 is that if you specify the wallpaper with an answer file, if you use a BMP it ignores it but a JPG works. What a weird thing to change.

Using an & changes the results to ignore. Probably because 'vista' isn't a valid function for that page, and there is no value for it either. Using & looks like it makes the search ignore the words afterwards. It is really a space, so %20, although you can use a + there if you want. http://www.catalog.update.microsoft.com/Search.aspx?q=KB3164033%20vista http://www.catalog.update.microsoft.com/Search.aspx?q=KB3164033+vista

Things to remember with the XML is that the boot.wim only uses the two windowsPE passes. And then, if you are using Setup to do the install, and use an answer file, it will only use that one. So say you have an XML with just the windowsPE passees in it and nothing else, then no other actions will be taken. Setup will ignore any XML that is in the image itself because you specified it to use another. But Setup always uses an answer file even if you don't specify the /unattend option. So installing using Setup will never use an answer file that already exists within an image. So you can do these two methods. 1. deploy with imagex/DISM, the answer file in the image (c:\windows\system32\sysprep\unattend.xml) is read on first boot after imaging. This XML does not have windowsPE phases. 2. deploy using Setup, the answer file has the windowsPE phases as well as the other things from the XML inside of the image. The other option of using WDS, you can specify a separate answer file for boot.wim and install.wim. This is the only method I know where you can use the two files like that.

I guess I've been asking for trouble my entire life!

Fix your topic title.

Can we get clarification on this 2nd XP, if it is a normal install or it is an XP made with nLite?

If it is a 0x7B on stage 2 of installation, the 2nd stage of XP install will be the reboot and it continues installing from the target/hard disk. Then it would likely mean that the hard drive is detected during stage 1 (text mode) meaning it is writeable but the OS cannot boot from it. If you are using an F6 driver, it may be the incorrect one. If you are not, then you likely need to find the correct one. Fortunately you have a working XP already, you can find the driver version from there.

Is this "tablet mode button" something needed when using a mobile device in actual tablet mode, where you have only a touchscreen to use and not a keyboard and mouse?

Really need to know exactly what the blue screen says. I can't remember, can you set XP to disable automatic restart on system failure?

This is one of the perks of the online game services, such as Steam with GTA V or Origin for BF4. A new Steam install can easily link to a Steam dir on another drive. I have done it already, and in case of Steam you can have it use multiple dirs on multiple drives. Not sure how exactly Origin works, I don't like it and will get rid of it as soon as I am done with BF4 myself. Otherwise, it is difficult to know. It would depend on the program itself, and this problem has been this way for many years. Some programs work just fine, even after the main OS is removed or replaced. Some just need registry entries restored, some will refuse to run on a new OS. You would have to handle it on a case-to-case basis. Another thing to watch out for, after you reinstall your OS, is that your storage drive have the same drive letter as it did on the previous OS.

Sure and it is probably LTSB, the only good Windows 10 edition!

People don't seem to mind because no one has broken into the place yet where MS is keeping all those keystrokes and wireless passwords.

Abadonware is determined by copyright, not active development. This is why MS software never ends up in the category of free distribution, no matter how old it is. Of course, they themselves can decide to release something if they want. Most often they do not, even for old software, which is disappointing.

I can't say for sure about legacy or "out of band" (aka things I don't deal with) but I never install wifi software on any systems I put a wireless card into. If the correct driver is used, then whatever the built-in stuff Windows has will work by itself. The only exception to that is Bluetooth combo cards, where the bluetooth does not work at all on the driver alone, or the manufacturer only provides and MSI or EXE for the driver.

Let us just hope it is only going to effect Windows Update and not the updates themselves. My last Win7 PC I built, I disabled Windows Update straight away. However, some times I did have to install an MSU due to other software requirements. For example, you can install H1Z1 on Windows 7 SP1 RTM x64, but it needs one update to work. They could really put the screws to people by blocking you from installing individual updates on these CPUs.

Look on this page, under "Installer Detection Technology" (there is no contents/targets for this page so use the search) https://technet.microsoft.com/en-us/library/cc709628(v=ws.10).aspx For any applications you write that should not be prompting for elevation, then you should create a Manifest for your program with such instructions.

Windows 8.1 Industry Pro has the same shortcomings that WES7 does, whereas if you do a full set using IBW, it will still leave some piece out. For 8.1, the part you need to do manually is related to USB. I believe that USB 2.0 is put in, but 3.0 will not work properly. I ran into this issue myself and it was not caught right away. I do not know about these other questions because I've only built this to OS to be an appliance. But you can test yourself by registering to get the eval version: https://www.microsoft.com/windowsembedded/en-us/downloads.aspx?

I've always seen the option in Process Explorer. You can try it and see if it is what you are wanting. I've not used it myself.

A lot of updates are like this, they do not do a real good job of explaining the things they correct. They seem to rely on people needing to know what they are doing, or in the usual case, install it if you don't know. When I first read this update, it sticks out to me (from my own experience) with SMB that you are then dealing with an in-network vulnerability. So, say some other system on your LAN sends a request to the unpatched system, then it could exploit whatever. BUT I do not know if you could fool Windows into responding to an SMB request through localhost, so then no other computers on the local network be needed. Update catalog only shows this for Vista, 2008 and POSReady2009. That Embedded variation, not being that different from XP (it installs like Vista) then the "cry rivers" response is because there is no way to update XP x64... Or Server 2003 which would be more of a concern. SMB is available in SP1 at least.

Welcome to the MSFN!

I thought Active-X was tied into Internet Explorer?

Hmmm well it does seem kinda weird that they would disable updates for everything just because one thing wasn't supported.

Do not post links to files not allowed for redistribution!