I've encountered both of these issues (cmd window not holding the reboot and the curious case of the missing mouse pointer).
I've learned to deal with the missing mouse pointer. I simply launch cmtrace, ctrl-o, then move the mouse until I see an indication that the mouse passed over it, then backtrack and try and move the progress window. Not ideal, for sure, but it's not impossible. On Fri, Nov 4, 2016 at 1:32 PM, Niall Brady <any...@gmail.com> wrote: > "In Windows 7, if you had an open command session, task sequence reboots > were held until the command session was closed. " > > > I've seen that too ! > > > On Fri, Nov 4, 2016 at 8:57 PM, Miller, Todd <todd-mil...@uiowa.edu> wrote: >> >> I feel like the problem is related in the same way that the BGInfo stuff >> works in WinPE and in Full OS Win 7, but is broken in 8 and 10. I am going >> to try executing a call to show cursor through the user32.dll and see if >> that can make the cursor come out of witness protection. >> >> >> >> For me it is quite tedious… When the task sequence fails, all the windows >> you open appear behind the large task sequence progress window in the middle >> of the screen… so Notepad opens behind that and I can see three or four >> lines of test above and below that window. Switching back to the command >> window – you cant see what you are typing because the task sequence progress >> window is covering two thirds of the command window. >> >> >> >> The other troubleshooting problem I have found is that when deploying >> Windows 10, an open CMD session will not prevent the computer from >> restarting in the task sequence. In Windows 7, if you had an open command >> session, task sequence reboots were held until the command session was >> closed. >> >> >> >> I wrote a 3-line autoit app that calls the user32.dll api for show cursor, >> but that didn’t work. L >> >> >> >> >> >> >> >> From: listsad...@lists.myitforum.com >> [mailto:listsad...@lists.myitforum.com] On Behalf Of Miller, Todd >> Sent: Friday, November 04, 2016 2:32 PM >> To: mdtosd@lists.myitforum.com >> Subject: RE: [MDT-OSD] RE: Windows 10 - mouse cursor gone during OSD >> >> >> >> Right, the problem cannot be related to WinPE version. The problem does >> not occur during the WinPE phase of the task sequence. The problem only is >> present in the FullOS portion of the OS Deployment. >> >> >> >> I saw a note in noobs about hibernating/then unhibernating the OS and >> that does work to bring back the mouse – but it is a really poor workaround. >> >> >> >> From: listsad...@lists.myitforum.com >> [mailto:listsad...@lists.myitforum.com] On Behalf Of Niall Brady >> Sent: Friday, November 04, 2016 1:47 PM >> To: mdtosd@lists.myitforum.com >> Subject: Re: [MDT-OSD] RE: Windows 10 - mouse cursor gone during OSD >> >> >> >> well using cm1606 with a boot wim from ADK 1607 on a lenovo thinkpad >> something or other today we saw no mouse cursor (heh), it makes >> troubleshooting harder when you are trying to scroll through logs in >> cmtrace, this bug might not be the same thing as the one in 1511 but it's >> the same result, no mouse cursor is visible at all during the in-Windows >> phase of OSD >> >> >> >> On Fri, Nov 4, 2016 at 6:42 PM, Michael Niehaus >> <michael.nieh...@microsoft.com> wrote: >> >> The confirmed bug in 1511 was related to the network initialization; that >> required applying a fix to replace a file in the boot image. That’s fixed >> in 1607. >> >> >> >> I don’t recall any mouse pointer issues. >> >> >> >> Thanks, >> >> -Michael >> >> >> >> From: listsad...@lists.myitforum.com >> [mailto:listsad...@lists.myitforum.com] On Behalf Of Niall Brady >> Sent: Friday, November 4, 2016 10:19 AM >> To: mdtosd@lists.myitforum.com >> Subject: Re: [MDT-OSD] RE: Windows 10 - mouse cursor gone during OSD >> >> >> >> Its in 1607 also fyi >> >> Sent from my phone, please excuse any typo's as a result. >> >> >> >> >> On 4 Nov 2016, at 16:05, Jason Sandys <ja...@sandys.us> wrote: >> >> There was a confirmed bug in WinPE 1511 that was supposed to be fixed in >> 1607. Don’t know if it truly got fixed or not. >> >> >> >> J >> >> >> >> From: listsad...@lists.myitforum.com >> [mailto:listsad...@lists.myitforum.com] On Behalf Of Miller, Todd >> Sent: Friday, November 4, 2016 9:24 AM >> To: mdtosd@lists.myitforum.com >> Subject: [MDT-OSD] RE: Windows 10 - mouse cursor gone during OSD >> >> >> >> I see this problem has been asked, but I don’t know if there was ever an >> answer. >> >> >> >> When I “F8” to open a command window during an OS Deployment of Windows >> 10, there is no mouse cursor displayed. The cursor is just hidden, the >> mouse still “works” it is just the pointer is no visible. It makes >> troubleshooting OS Deployment difficult to impossible because the only real >> action you can do is with the keyboard. Windows get in the way of what you >> are looking at – it is just really difficult to maneuver in the OS without >> the mouse cursor. >> >> >> >> Has anyone figured out a good way to recover the cursor? This is really >> tedious. Anything in the Unattend.xml that could counteract this effect or >> maybe some command In the TS that could run after reboot to show the mouse. >> It feels like whatever process is hiding the desktop with the black screen >> is also hiding the mouse. So frustrating. >> >> >> >> The cursor is present in WinPE stages, but not full OS. It is also fine >> from the same boot media in Windows 7 deployment. >> >> >> >> From: listsad...@lists.myitforum.com >> [mailto:listsad...@lists.myitforum.com] On Behalf Of Murray, Mike >> Sent: Wednesday, February 17, 2016 11:37 AM >> To: mdtosd@lists.myitforum.com >> Subject: [MDT-OSD] Windows 10 - mouse cursor gone during OSD >> >> >> >> Anyone else have this problem. If my TS bombs out for any reason, if I >> want to troubleshoot I have no mouse pointer. The mouse “works” (I can >> blindly click around and see things happen), but there’s no pointer. >> >> >> >> >> >> Best Regards, >> >> >> >> Mike Murray >> >> Desktop Management Coordinator - IT Support Services >> >> California State University, Chico >> >> 530.898.4357 >> mmur...@csuchico.edu >> >> >> >> >> >> >> >> ________________________________ >> >> Notice: This UI Health Care e-mail (including attachments) is covered by >> the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521 and is >> intended only for the use of the individual or entity to which it is >> addressed, and may contain information that is privileged, confidential, and >> exempt from disclosure under applicable law. If you are not the intended >> recipient, any dissemination, distribution or copying of this communication >> is strictly prohibited. If you have received this communication in error, >> please notify the sender immediately and delete or destroy all copies of the >> original message and attachments thereto. Email sent to or from UI Health >> Care may be retained as required by law or regulation. Thank you. >> >> ________________________________ >> >> >> >> >> >> ________________________________ >> >> Notice: This UI Health Care e-mail (including attachments) is covered by >> the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521 and is >> intended only for the use of the individual or entity to which it is >> addressed, and may contain information that is privileged, confidential, and >> exempt from disclosure under applicable law. If you are not the intended >> recipient, any dissemination, distribution or copying of this communication >> is strictly prohibited. If you have received this communication in error, >> please notify the sender immediately and delete or destroy all copies of the >> original message and attachments thereto. Email sent to or from UI Health >> Care may be retained as required by law or regulation. Thank you. >> >> ________________________________ >> >> >> ________________________________ >> Notice: This UI Health Care e-mail (including attachments) is covered by >> the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521 and is >> intended only for the use of the individual or entity to which it is >> addressed, and may contain information that is privileged, confidential, and >> exempt from disclosure under applicable law. If you are not the intended >> recipient, any dissemination, distribution or copying of this communication >> is strictly prohibited. If you have received this communication in error, >> please notify the sender immediately and delete or destroy all copies of the >> original message and attachments thereto. Email sent to or from UI Health >> Care may be retained as required by law or regulation. Thank you. >> ________________________________ > >
