But, if regular updating goes away in Windows 10, why would you need to troubleshoot?
<stirring the pot> From: [email protected] [mailto:[email protected]] On Behalf Of Garth Jones Sent: Wednesday, March 4, 2015 10:33 AM To: [email protected] Subject: RE: [mssms] Wow ? Look how invol ved reading the Windows 10 Win d ows Update log may become I think that it should be added into CMtrace to read the log files!! Otherwise it will be impossible for anyone to troubleshoot WUA issues! From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Rod Trent Sent: Wednesday, March 4, 2015 10:18 AM To: [email protected] <mailto:[email protected]> Subject: RE: [mssms] Wow ? Look how invol ved reading the Windows 10 Win d ows Update log may become It’s supposed to get better, but yes, it does make it more difficult. P.S. I wrote about it here: http://winsupersite.com/windows-10/microsoft-makes-troubleshooting-windows-update-windows-10-tad-bit-more-difficult From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Robert Hastings Sent: Wednesday, March 4, 2015 10:07 AM To: [email protected] <mailto:[email protected]> Subject: [mssms] Wow � Look how involved reading the Windows 10 Win dows Update log may become I was forwarded this link which outlines the purposed process for reading the Windows Update log in Windows 10. I can’t figure out why they want to make this so difficult. This might be a good blog post on My IT Forum… I provide some feedback under the “Give Feedback” section. So much for reading logs with Notepad.... http://support.microsoft.com/kb/3036646
