So what you think should be the Focus of Windows. I think Security is a good primary focus but one or two of these should be a new focus without forgetting security.
A: A version of Windows that centers on fixes, updates, upgrades and polish. Big new features postponed to next major version. If XP would have a dozen big SP2 style updates, the difference between the old and the new version should equate to that dozen. Lot of attention to details and polish and postponed things.
B: UI and usability re-think for other than just Office. Change pixel relative controls to more advanced ones that do not base on the display resolution. Intro controls that change with the interface but surface the same data to developers, so that whether you use keys, mouse, touch or even some more in the future ones such as eye and brain-connection to operate the control, it will always be the best possible usability, accuracy, ease, speed and such for the program without changing line of the underlying program code.
C: Start over with the OS in such manner that no native code is carried over but pure-.NET, zero pinvoke programs would still work more directly, meaning little or no porting work for most .NET apps. .NET itself would be thoroughly ported to the new foundation,
which for example could be based on the Singularity research. Native apps or services calling to Win32 would still be available for use but in their own context. ISV and third parties can do the primary work where direct bridging of data between applications
and services running in the legacy context and the new is necessary.
Legacy drivers would continue to work in the new OS inside a legacy context and have an abstracted bridge for communication. If for example legacy network driver "bsods", it would only bsod one legacy driver context in the background, disabling the network connectivity for the new OS.
Thus a huge number of legacy drivers would continue to work where there is a generic bridge available but be isolated from the new foreground OS and other drivers. The bridge could use the existing abstractions by mapping current win32/user mode calls to new communication pipe between the legacy context and the new OS.