Announcing Windows 10 Insider Preview Build 16237 PC for Fast ring Insider

blackroseMD1 said:

Yeah, I'd seen that you said your issues had been fixed. Mine still haven't, unfortunately, at least on an upgrade install. I finally just bit the bullet and did a clean install with this new build. I'll get to testing gaming once I'm off work. Got my fingers crossed that I can enter buildings in GTA again without the GraphicsPerfSvc service stopping and restarting which causes graphics to hang.

Sorry to hear that--all my builds are upgrades--it's been well over a year since my last clean install. Good luck--hope your problems get sorted!

16237.1001 installed without any hiccups for me. First time for several builds that there has been no drama. And I had Vipre, Malwarebytes Pro, CryptoPrevent installed and running when the update process started. All my internal drives and peripherals were connected.
Alt+keys codes is working here in FF, and in Notepadd ++. FF remained as my default browser, and System Protection remained enabled.
It was a slow update, I didn't time it precisely, but about 2 hours. More time on the "Installing updates" (I like the new % reporting) than on the "Working on updates" segments. And this time "Working on updates" stayed on my primary monitor, I think. I left my desk at the start of that segment, and when I returned it was at 55% on my primary monitor. During previous updates the display has switched to my 3rd monitor (onboard graphics) for the 32% to 75% segment

Don't know if anyone else is having this particular problem, but this is the second recent IP build I've had this problem with and I *thought* it was Microsoft disabling Adobe Acrobat Reader DC to force me to run Edge as my default .pdf reader (which really stinks, btw, compared to Acro reader DC.) Well, turns out it has nothing to do with Windows IP builds...it's a misconfiguration problem Adobe Reader has with a couple of the IP builds, including 16237, apparently. Reader DC version 17.009.20044.

What happened is that Adobe reader DC wasn't uninstalled by the installation of 16237, had all of its defaults, and would run from the desktop or by double-clicking a .pdf--but without opening a screen! Only way to know it was indeed running was to check the Task Manager, of course. The last time that happened I fixed it by uninstalling and reinstalling reader DC, and I chalked it off as a one-time fluke. This time the reinstall didn't work at all. So I thought it might be a conflict with a recent driver install, or one of the little programs I run at boot, so I booted into safe mode under 16237 to see if Reader would open there. It opened--but not to the main application! Instead, I got a fairly large requester generated by the Reader program (easy to see since safe mode opens low res) that informed me that my OS was incompatible with Reader's Protected Mode configuration, and I got the choice of options to either turn it off permanently (which I did) or to turn it off just once. I applied my choice to the Adobe Reader program, and it then opened fine in safe mode, so I rebooted to normal mode and now the program is running fine.

Apparently, the default install mode of Reader DC is to its own protected mode--that is incompatible with this build of Windows. Still have no idea why the option to turn off Protected Mode did not open from my desktop, but only in safe mode. Thought I might pass this on if anyone else sees this particular problem.

Build looks fine, so far--no problem upgrading--very smooth and quick.

All in!!!



Too late to look around though.
I'll take a closer look tomorrow.

So, apparently Windows doesn't think I have DX9 installed despite me installing the June 2010 redistributables. Makes it so that I can't download a lot of apps.