Just noticed KB3066096 myself. Thank you.
It will require a restart afterwards.
Windows Update - Check for and Install in Windows 10
Last edited by Brink; 27 May 2015 at 08:22. Reason: addition
After I had installed this, I found it need a restart. Even after a restart, it still showed, in the history, that it needed a restart.
Going back to the old system (Control Panel - Programs and features - update history) shows it is, in fact, installed. Must be yet another bug. BUT, as everything appears to be normal. I am ignoring it until the next build. I have logged it as a bug on the insider, though.
Telemetry reports for Windows Insider Preview do not include the build number (KB3066096)
Symptoms When you send telemetry reports to Microsoft for Windows 10 Insider Preview, the build number is not included in the telemetry report. Resolution An update is available to resolve this problem. How to obtain this update Windows Update
This update is available from Windows Update.
Prerequisites To apply this update, you must be running Windows 10 Insider Preview Build 10122. Restart information You must restart the computer after you apply this update. Update replacement information This update does not replace any previously released update.
Quite honestly, I am not sure I know what a "telemetry " report is. But in the MS context, isn't that something in Windows Office?
Anyway, I put mine in in the insider feedback facility.
Yes, when I installed it last night, after restart, the notification area said it needed a restart to finish installing. Because, since Build 10074, it sometimes has been taking 2 or 3 tries to install updates, I just restarted again. When I checked, in the All Settings update area, it said it needed to restart to finish installing. Like Davehc, I checked the programs and it said was successful. Guess I better 'me too' his report. Build 10122.
I'm getting the requires a restart to finish installing also. I noticed that you can select to delay upgrades.
A Telemetry report can be a lot of different things. Microsoft creates Telemetry conditions, such as "User clicked start button", however this contains a host of information, such as build number, date/time, userid, how long it took to respond, etc... Then, they can aggregate this information in their database and run statistical models on it... such as "how many times did the user click the start button in a day". how frequent was it? minimum time between clicks, average response time. How long did they keep the menu open? Did they always select an icon? DId they choose a win32 app or a Universal app? Was it from the all apps or from the pinned apps? etc...
This allows them to make decisions about what is and isn't important, and make decisions about changes that need to be made. For instance, if the start menu is taking an average of 3 seconds to open, they know they need to speed it up.