Alright, I figured that I probably wouldn't get an answer on that one, so I had to solve it myself.
And since I can repeat that behavior, it looks like a weird bug. Assumptions: CM2012, R2, CU4 (not sure if it happened before) CM created image to deploy, but also happened with "install.wim" MDT based TS, vanilla. Boot image with F8 enabled (doh) Basically it all looks good and F8 is also working once booted into the OS. But, if you enable "do not assign." here, in the preinstall part on the BDE volume, which I think is valid for whatever reason, F8 function in the OS breaks. What happens is a cmd is opened, but you can't see it. Hence you can't close it and if you can't close it, the screen gets stuck once the TS wants to reboot. If that happens you have the same behavior. Can someone try to duplicate that? You only need to have F8 enabled and tick that checkbox. At least that's what I did. If you add a step to get a cmd open (serviceui.exe) you could open taskmanager and see that every F8 hit creates a new cmd you can't see. But why would that option have anything to do with F8 support? -Roland From: [email protected] [mailto:[email protected]] On Behalf Of Roland Janus Sent: Freitag, 27. Februar 2015 11:12 To: [email protected] Subject: [mssms] F8 in OS creates invisible cmd processes I know this sounds weird, but that's what's happening now. The boot image has F8 enabled, it works fine in Win8 deployments and in PE in general. But when I deploy Win 7, where it still works in PE, it doesn't in the full OS. I figured that it does create the process, but the window doesn't show, which means it can't be closed either. That causes reboots to hang. To get proof, I've used serviceui.exe to open a cmd and have it wait and then press F8. The processes are there, but not visible. Whenever I use F8 another invisible process is created Process list: I don't know if the setupcomplete.cmd is supposed to be there. The first one is from the serviceui, the others are the hidden ones. They are the same, but don't behave the same. It worked in the past but now something changed and I can't put my finger on it. Tried like everything, maybe it's a patch, so I've used a plain OS, even the original install.wim, but no difference. I thought maybe CU4, so I removed that for the client, also no difference. That is so weird. Anyone? -Roland
