Just beyond a minor disaster
Fortunately there was no major damage or otherwise "crashed" systems, but the danger was there. Because the "escaped" build 18947 was hardly tested and the whole thing could have been pretty clear. At the beginning Microsoft did not speak, certainly because they first had to figure out how something like that could happen.
In the meantime, the company has gone to the bottom. Last night followed by Twitter and then the announcement that the unintentionally published build had affected only a "very limited number" of Windows insiders. If that was the case, he should read a forum post, so that Insider Twitter account from Microsoft (via Dr. Windows).
In the forum Microsoft explains how you can go back to an earlier version and reveal what happened. For example, an incorrect configuration change on the server resulted in the build being distributed not only internally, but across all rings. Even in the "safe" slow ring, some users got this potentially unstable version.
For users who show build 18947, which has already landed on the machine and are waiting for installation, updates must be interrupted for seven days, which should cause the device to disappear rather quickly.
Also see: Windows 10 – Microsoft accidentally sends untested build 18947
(t) Windows (t) Windows (t) Windows (t) Insider (t) Insider Preview (t) Build 18947 (t) Software (t) Operating Systems