Fun nuances of Win10 and what to do about it

I accidentally discovered some funny nuances of Win10, which can be very troublesome for users. But who warned - that is armed.

1. Safe-mode & Win10
2. Cyclic restart when installing updates.

1. Safe-mode

As it turned out, in win10, the ability to start safe mode (safe-mode) was removed by default when Windows started. Now, in order to get this opportunity, it is necessary on the WORKING Windows, that is, in advance, to execute the command as administrator
')

bcdedit /set {default} bootmenupolicy legacy 

And only after such manipulations the good old F8 will give an opportunity to get into the system start selection menu.

This is best done with such a batch file running as administrator (the displaybootmenu command from practice is not really needed but it is recommended to set it as well):

 @echo off bcdedit /set {bootmgr} displaybootmenu yes bcdedit /set {default} bootmenupolicy legacy timeout 20 exit 

To return to normal mode by default, replace legacy with standard .

In addition, some global updates reset this setting to standard , therefore I advise you to explicitly set the parameter before rebooting after any changes in the system, well, or through the scheduler for the logoff event (although this is probably a brute force).

If all the same trouble happened and you need to get into safe-mode, win10 does not load anymore and the F8 call was not turned on, that is, two options.

a) in some cases it helps 3-4 times forcibly with a reset to interrupt the download and then win10 will offer to enter safe-mode. This method did not help me, but my colleague at the neighboring workplace did it.

b) boot from the boot image (disk, flash drive, "resuscitators"). During loading, press shift-F10 to enter the command line. We look at what letter your boot disk is mounted in a particular case. If this is not (most often), then manually mount

 diskpart select disk 0 select partition 1 assign letter=s exit 

(choose physical disk 0, that is, the first in BIOS, section 1 is the one that is hidden as a system backup. If you have a slightly different hard disk configuration, correct the commands).

View the list of sections:

 diskpart list volume exit 

then

 bcdedit /store s:\boot\bcd /set {bootmgr} displaybootmenu yes bcdedit /store s:\boot\bcd /set {default} bootmenupolicy legacy exit 

after which the menu should appear.

2. Cyclic restart when installing updates.

Here manifested notable trolling MS. In Win10, in addition to the standard regional settings like Russia, Ukraine, Kazakhstan, several additional “Russian (Ukraine)”, “Russian (Kazakhstan)”, etc. appeared. When choosing which region the Ukraine, Kazakhstan etc. is exposed, but the system Windows notifications go in Russian and not in the national language.

So, when choosing one of these non-standard regional settings, with a high probability, the Win10 update does not reach the finish line and goes into an endless automatic reboot. On standard regions such as Russia, Ukraine, Kazakhstan - I have never seen such an effect. Actually, the solution to the problem is to set the setting to a standard region. If you manage to enter safe-mode - set it there. I did not succeed, because the solution with the boot image. Similar to the above, we get to the command line.

 diskpart select disk 0 select partition 2 assign letter=w exit 

(choose the physical disk 0, that is, the first one in the BIOS, section 2, the one on which Win10 is actually installed (!) is not hidden.)

 Dism /image:W: /Set-AllIntl:ru-RU exit 

After a reboot, the update is correctly installed and everything works, just re-set the regional settings. If you still consider it necessary)

Ps. Win10, like WinSRV 2012 and higher, is becoming more and more like Unix. More and more important, but hidden, settings can be changed exclusively (or, at least, much easier and more convenient) from the command line. Or download additional utilities. The next step is to replace the registry with text files).