I have not clean installed 17035 yet, but I have tested this by clean installing version 1709 on dual boot on same machine, then upgrading it to 17035. Got same issue, Files on Demand is broken. I've reported this in Feedback Hub, upvoted other feedback with same issue, and posted on Twitter:
Tweet
— Twitter API (@user) View on Twitter
One reply from Insider team:
Tweet
— Twitter API (@user) View on Twitter
The only question for people using an AMD processor is whether build 17040 will be released Wed or Thursday. At least Microsoft could do us the courtesy of saying whether or not we can test.
Are you serious??? You seriously don't know the history between Intel and AMD? AMD was putting their foot in Intel's a$$ back in the late 1990's, and Intel changed the architecture of chipsets and other mobo pieces to specifically put AMD's BETTER architecture at a huge disadvantage. They almost put AMD out of business, and it has taken them more than a decade and a half to come back from it. Google it, this is just one example of all the things they did. They also manipulated benchmark software to favor Intel chips over AMD chips. There was an entire host of major things Intel did, because they basically had a monopoly until AMD came along, and all the manufacturers were at Intel's whim. This is well documented information.
I personally haven't bought an Intel chip as soon as I had a choice. They did not acknowledge a flaw in their floating point logic in the 386 for many months. The moniker "Wintel" was coined for good reason. I just hope this build 17035 is a one off.
Yes, MS and Intel cooperated ever since beginning of PCs as such. At times of 8088 and 8086 there were other and better CPUs on the market but it was IBM that choose Intel CPUs so most of the "blame" should go to IBM. Gates and company worked with and made deals with IBM, IBM with Intel and here we are.
Apple, Atari, Commodore and others were jealously holding to their OSs and systems not letting anybody from side in and IBM mistakenly wrote off personal computers as trivial and let MS and others into their system. Any other system was seen as just a game machine and not a serious business computers until it was to late and only real PC was considered IBM with Intel. So it came to be that only "real PC" was with Intel and it still persists.
Intel just took on the opportunity while Motorola, Zilog, Tandy etc. and later on AMD and Cyrix were just too late to the game. It's ultimate goal of any corporation to have monopoly on their products and get as close as possible to it by any means.
i bought my tandy trs-80 when it came out, the first one shipped to delaware. it had an intel 8086, bought an 8087 for it later. tandy OS, and a basic imterpreter, but later i bought it a couple of 5.25in. floppy drives. eventually shifted to an 8086 cp/m machine, it also came with mdsdos, 8in. floppies, and a microsoft basic compiler. msdos came with source code so i could compile it to include drivers for my hardware. progressed up the years to my current i7 & have stuck with intel ever since. heard too many horror stories about people trying to run intel code on amd cpus, untrue or not, it was/is the industry standard and all others have had compatibility troubles emulating a real intel instruction set, right or wrong. (intel of course emulates amd x64 extensions, another can of worms). anyhow, amd may technically have a better processor, but history has not been kind to amd compatibility with intel. anyhow, i stick with intel, as then microsoft and/or other software providers cannot say something doesn't work because i have an oddball amd cpu.
Today I tried to download the 17035 build from my AMD E 350 processor and it showed the computer as up to date. It means that Microsoft has NOT yet fixed the bug with AMD processors or that Microsoft is not bothered about AMD owners and will go ahead with the next build, probably 17041 or 17042. Whether the AMD bug will be carried over to the next build is a moot point.
Quote