Forums typically illustrate the problems encountered by users of a product, whether software, hardware, or user created, all of which are negative. Many times, products get negative feedback simply because the user had false or unrealistic expectations, or did not do enough research beforehand. Rarely do users go to the forum to discuss a positive experience.
Well, I want to report a positive experience, specifically with the Intel Compute Stick.
I installed Windows 10 Home edition (32-bit) on my stick some months ago. Because I have been traveling for the past two months, I had not had the opportunity to use the stick, or apply the fall update that seems to have caused problems for so many. I had some free time during the holiday, and took the opportunity to update my stick.
Before beginning, I backed up any data I wanted to keep to the SD card, and made sure that my SD card was removed afterwards. Then, I made certain that I had a wired mouse and keyboard connected, and that no other external devices were connected via my USB hub. I also made sure the stick was using the supplied power adaptor.
I began by updating the BIOS using the usual F7 path, using a partition formatted as FAT32 where I had downloaded the .BIO file. No problems were encountered, and I booted to Windows.
At this point, to be safe, I disabled write-caching for the disk, the result of reading and researching before I attempted to update Windows 10.
Then, I started the update process for Windows 10. Before attempting any of this, I did a little research, and used this document as a guide:
There were a number of updates, including the fall update (build 10586). All of the updates installed correctly, the only problem being the download time for build 10586.
As I sat watching the progress bar, I kept waiting for problems to occur. Yet, there were no problems. All updates, including the fall update, went perfectly.
Next, I decided to update my drivers from the Intel site. Again, all went as it should and the experience was unremarkable. For the drivers, I used this link
Then, I decided to update any device drivers I could find in the Device Manager, typically found under "System Devices". There were probably ten or so that needed updating. How did I know which to update? Rather than right-clicking on each device and selecting "Update Driver Software", I used a Microsoft utility to "tell" me which devices needed updating. To help with this, I downloaded the utility at this link: https://support.microsoft.com/en-us/kb/3073930 https://support.microsoft.com/en-us/kb/3073930 . The utility is intended to allow you to hide updates you may not want. However, if you select "Hide Updates", you are presented with a list of updates, many of which will be system devices. I did not "check" any of the boxes. Instead, I simply used the list as a guide. I could now go directly to the device in the device manager, right-cli...
Yes thats nice for you that you did not used your stick for a long time and did not suffer from the automatic windows update procedure and you have been lucky enough to reed from the update problems before...
Thanks, Al, for letting others know of your experience with successfully installing the November update. Not only are your procedures admirably thorough, but it highlights that there must be some difference between your situation and those of others like me who have had serious problems.
I would be interested to know how much free disk space and what paging file size/settings you had when you did the update? I suspect it may be these factors that make the main difference between a successful and unsuccessful update. I've set out my experience, and how I was able finally to get the update fully working at .
Man, you mean that this whole time, all I had to do was just update the BIOS and disable write-caching before Microsoft automatically pushed out their updates?!?! On a slightly less sarcastic note, I got this link from Intel Customer Support as an answer to why the 3 brand new ComputeSticks I purchased a month ago (pre-loaded with Win10) won't complete a standard Windows Update. There is zero reason whatsoever that a person should have to "read and research before updating Windows" on a stock machine, ESPECIALLY when Microsoft is pushing these updates out automatically. If the machine requires that kind of prep just to successfully perform a standard Windows Update, then said machine is not ready to be on the market. My 2 cents...