New
#130
Since the VMware problem is on Windows Insider hosts I'm not so sure VMware will go out of its way to patch its executable - such a host is of course unsupported. Sometimes the problem will go away in the next build. If the problem persists with no resolution I'll almost be tempted to install a Windows IP on my hard drive - but probably not. I found a workaround for a problem with VMware Linux that plagued me for years and now can enjoy 3-D acceleration on my VMs. If, as jimbo pointed out, MS had better QA that would be a plus but they really aren;t listening to feedback from anybody except corporations. Or so it seems
Agree..
From announcement:
REMINDER: As is normal with builds early in the development cycle, builds may contain bugs that might be painful for some. If this makes you uncomfortable, you may want to consider switching to the Slow ring. Slow ring builds will continue to be higher quality.
Some days ago (10+ IIRC) I used the Windows Insider Program page in Settings to set my Surface Pro 4 to the Preview ring. It was running build 18282. Days passed without it changing the installed OS, so after build 18290 was issued I reverted to fast ring, again using the settings page. Several days passed, and every time I ran WU I was told that my system was up to date. I looked at this registry key:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability
and found that the Ring entry was WIS, NOT WIF as I expected it to be. It appears that my attempt to reset to "Active" and "Fast" in the Windows Insider Program did not get carried through to the registry.
I modified the registry key, rebooted, and checked WU. The update was available and Surface Pro 4 is now running build 18290.
Reported to Feedback Hub.
Marty, these days with the Insider editions being the next coming release of Windows to the public, it only makes sense to support it, making sure all is well before Windows hits the masses. I've seen the results of not supporting the Insiders editions, a major disaster upon release of Windows...
Marty, these days with the Insider editions being the next coming release of Windows to the public, it only makes sense to support it, making sure all is well before Windows hits the masses. I've seen the results of not supporting the Insiders editions, a major disaster upon release of Windows...
Actually, I was mostly talking about VMware's support policies, although my post was very meandering. We might even find out tomorrow (Weds) whether the problem is transient.
I can confirm, that regarding Rainbow Six Siege game, even on the latest game patch (Wind Bastion) issue with Windows Insider 18290 it's STILL present, BSOD on anticheat loading phase. Every build after 18277 render every Battleye games UNPLAYABLE.