Announcing Windows 10 Insider Preview Build 16188 PC and 15210 Mobile Insider

cereberus · 05 May 2017

Edwin said:

I wish they would do away with the friggin Lock Screen! Serves no purpose whatsoever!

The old ways of disabling it work again - see tutorial

Enable or Disable Lock Screen in Windows 10 - Windows 10 Customization Tutorials

Berton · 05 May 2017

Edwin said:

I wish they would do away with the friggin Lock Screen! Serves no purpose whatsoever!

Oh???? I find it quite useful and necessary as treasurer for our church. When needing to step away from the computer and out of the office for a few minutes I don't have to shut down QuickBooks [close company] first, just press Windows key plus L. Of course it works best when having to use a password to log into Windows and the Lock Screen.

meebers · 05 May 2017

cereberus said:

The old ways of disabling it work again - see tutorial

Enable or Disable Lock Screen in Windows 10 - Windows 10 Customization Tutorials

Us old geezers find it interesting to follow the methods to do so

sassafras · 05 May 2017

Wynona said:

I just tried it and it doesn't work for me either.

I kinda like a new view every so often. :)

Same here. They present some beautiful pictures!

dencal · 05 May 2017

wen said:

Like a Fool, I tried installing Build 16188 again and it fully installed.

I tried MS Outlook 2016 and it worked for two minutes, until I tried to compose email.
It errored and locked up. then displayed this:
Attachment 133666
Rebooted and tried to access Address Book:
Attachment 133666
I did what it instructed, delete .ost file and it will rebuild upon Reboot.

It slowly pulled off files from it's Exchange Server. Then I tried composing new email again and same error as pictured above.

Attachment 133668

Do remove your e-mail address in your post, or you could be compromised.

f14tomcat · 05 May 2017

martyfelker said:

You probably have done this already but if you have two Windows OS, even with separate partitions, it is safest to make sure neither Windows is aware of the other. Do this using Disk Management and remove the drive letters from the foreign OS. Say Insider is on the first partition and 1703 on the second. Then you don't want to see a D: drive from either. This doesn't explain the problem with your graphics cards however.

Marty, thanks. Been doing that since start of Insider. I do it with a quick .reg file, one on each partition (RTM & Insider) to hide each from the other. I have in the way past been bitten by cross-pollination! Particularly during an update. I click it and reboot.

Code is:

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices\Offline]
"\\DosDevices\\F:"=dword:00000001

linw · 05 May 2017

Woke comp this morning to find it at the lock screen. Funny, I said, must have been an update!

It struggled with sorting itself out as Taskbar items took a while to appear. Then noticed the Notification/Settings wouldn't open.

Shutdown and restart fixed everything spot on (I don't run Outlook!!).

But funny I didn't get the "Hi etc" setup stuff.

Anyway, happy as usual - one of the Blessed ones:)

fdegrove · 05 May 2017

Hi,

f14tomcat said:

Marty, thanks. Been doing that since start of Insider. I do it with a quick .reg file, one on each partition (RTM & Insider) to hide each from the other. I have in the way past been bitten by cross-pollination! Particularly during an update. I click it and reboot.

Et voila, you do not want to invite "crosspollination" .

Cheers,

Code is:

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices\Offline]
"\\DosDevices\\F:"=dword:00000001

smactilactus · 05 May 2017

f14tomcat said:

Marty, thanks. Been doing that since start of Insider. I do it with a quick .reg file, one on each partition (RTM & Insider) to hide each from the other. I have in the way past been bitten by cross-pollination! Particularly during an update. I click it and reboot.Code is:

Code:

Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices\Offline]"\\DosDevices\\F:"=dword:00000001

sorry, but that is a bit confusing to me. Why would os's that are on completely different partitions have anything to do with one another???? And how does it affect each other? I have been dual booting on the same pcie drive for years, and have never heard anything about this. i have a 500gb pcie m.2 drive, and split it into two equal partitions. one has my fast insider build, and the other has my slow ring build. i show both systems on each others partition. so i would love to know what the deal is with this. maybe it is at the root of my upgrade woes...?

martyfelker · 05 May 2017

Thank you for this interesting code. I was imprecise in the way I described what you aptly call "cross-pollination" ]. It's been a long time since I made a mistake and confused windows system programs between two Windows installations. My main problem (actually I've downgraded this to an annoyance:)) is the Windows Bootloader. If you use the Windo9ws Bootloader you will reset the machine if you switch between Windows 10 and Windows Server 2016. To avoid this I use Terabyteunlimited's Boot it Bare Metal program (been using Terabyteunlimited since the mid -90's). I use BCDedit and copy the Windows BCD store from (in this case) the Windows Server 2016 partition to the Windows 10 partition. That means I can directly boot into either OS. Actually my setup is a bit more complex since I'm actually triple booting with openSUSE. In openSUSE using BTBM I can disable the grub os-prober which I no longer need. So I have 4 primary partitions and can stick with MBR rathar than use EFI. Since playing with operating system is one of my main diversions I use VMware, Virtualbox and Hyper-V to satisfy my lust for novelty.