You ticked the options, created the USB, and Windows still asked for a Microsoft account. Before blaming the headline bug, work through the ordinary causes - together they explain far more ignored-settings stories than any single defect.
The 4.14 dialog did have a real fault - the first option could stay checked by itself - but it is only one entry on this list. The rest are process mistakes and moving targets, and they will keep happening on every future version until the habits below replace them.
The Windows User Experience dialog appears when you press Start, and the answer file is written as part of that creation run. If you created the USB, then changed your mind about options, nothing on the stick changed - your new intentions never left the dialog you cancelled. The same trap catches people who keep one 'universal' stick and assume plugging it into Rufus updates it. It does not. Options only exist on media created after they were chosen.
A common workshop habit breaks custom installs quietly: creating the stick with Rufus, then 'refreshing' it by copying a newer ISO's files over the top, or merging folders from an older stick. That can replace or orphan the answer file, or leave an older one pointing at the wrong image. If a stick's history involves manual file surgery, stop diagnosing the options - recreate it cleanly with Rufus from one ISO and test again. Unattended installs are chains; a hand-edited link invalidates the whole chain.
Setup screens are not a fixed contract. Microsoft adjusts the out-of-box experience between feature updates - new prompts appear, old ones move, account flows change - and an answer file written for one build can partially miss on the next. Rufus's own history shows the chase: options appear in its dialog specifically to counter new setup behaviour in new Windows builds. If your options were honoured last year and are half-ignored on a fresh ISO, suspect the ISO's build before the tool, and make sure your Rufus is at least as new as your ISO.
On 4.14 builds, the first Windows User Experience checkbox - the hardware-requirements bypass - was reported to come back checked by default even after being cleared, which 4.15's changelog confirms and fixes ('first WUE option always being checked by default'). The username got stricter treatment in the same fix release, and an earlier 4.14 changelog line already admitted trouble with local accounts whose names begin or end with a space. If your symptom is an option being on that you switched off, on a 4.14 build, you have found the genuine article - update, recreate, move on.
The video covers the famous cause; this page covers the rest of the list. Watch it, then check your own stick against suspects one and two before blaming the software.
▶️ Watch Full VideoPlug the USB in and look at its contents in File Explorer - a customised Rufus stick carries the autounattend.xml answer file where Setup can find it on the media. No file means no customisation was applied during creation, whatever you remember ticking.
Partial honouring usually points at the moving-target cause: the answer file was read, but one of its answers no longer matches what the newer Windows build asks. A fully ignored set points at process causes instead - an old stick, or files copied by hand.
Only after recreating the stick cleanly with a current build and a single untouched ISO, and watching it fail again. Reports that survive that test, with the exact version and ISO build named, are the ones that get fixed - the 4.15 changelog is proof the process works.