If you ask about UUP: If you ask for general WU, CU is just an update, Feature Update is a full upgrade to a new build.
so for the most clean 1809 17763.1 x64, i should download "Feature update to Windows 10, version 1809 (17763.1) amd64" ? and the same for 1903 when it will be available ? sorry for OT 1809
Hi. Any easy way to avoid the this machine cannot be upgrade to windows 10? Im getting this message on 1903 installer whrn upgrading from 1809. According to MS it's because usb drives. But dont have any on this computer. Thanks.
beta driver out for X-Fi Titanium HD SB1270 ONLY (other x-fi allegedly coming soon) www .reddit .com/r/SoundBlasterOfficial/comments/blf2z1/titanium_hd_driver_fix_for_windows_rs6_1903/ (remove the spaces because i'm not allowed to post links yet) Posted to dedicated topic as well, but I thought I'd leave it here too.
I would do a Clean Install. Maybe some of your drivers e.g. graphics card need to be updated first before upgrading to 1903.
Hi. Yes .Works fine that way. But not able to do clean install on every pc. Hope there is a real solution. Probable some non removable drive is causing this. Tried to update drivers but still the same.
OK so I'm interesting to know what type of PC you're having issue with?desktop/laptop? model? brand? it may help.
Hi. It's a super common build. Desktop z97 i5 haswell, gtx970. I guess I ll wait for the public release. The error gives a link to MS support where it says the installer has problems with usb pendrives or just drives. Try removing them or wait for an update. Thats their suggestion. I thought maybe downloading another build could work. I just made an iso based on 18362.1 through uuuup downloader. Maybe will try a higher 18362.xx build.
I see. Was guessing it's an OEM desktop/laptop or something. Well do you have more than 1 HDD/SSD? The error you are seeing is all about drive letter assignment if I remember correctly. Let's see what happens next week. Maybe integrading new CU/SSU fix the issue.
Just one ssd and one hdd. Super normal pc build. Yes, i think is the drive assignment problem. Will try integrating some cu/ssu. Thanks
It probably is more like a compatibility issue, if this was common, we all would have seen this happen, when 18362.1 became available several weeks ago.
We should be getting a CU in a couple of days to fix the drive assignment bug by MS schedule, OEMs already have 18362