Why does the computer immediately reboot when changing the network type?

Question

Computer networks

The office has two machines: a Windows 10 laptop and a Windows 7 desktop. Both machines are connected to the same router, the laptop via Wi-Fi, and the desktop via Lan, respectively. The task is as follows: set up a local network between devices, and enable printer sharing from a desktop computer.
The problem is simple, and I wouldn't be asking questions like this if it weren't for the next problem. The thing is that the desktop computer categorically refuses to share over the network, and creates a headache when trying to configure it. When you try to change the network type from “public”, to “home” or “enterprise network”, the computer instantly goes into reboot.
I read in one article that this error is related to incorrect installation of updates, and in order to solve it, you need to use "Windows recovery" - an ingenious solution that is absolutely not suitable for the computer of a very nervous chief accountant. Information also varies on the forums - someone says that the problem is in the equipment, someone complains about a magical "network virus".
Tomorrow it will be necessary to solve this problem in a timely manner, and very quickly, so there is no time for long picking now, and I would like to get a more or less intelligible answer, well, or a guideline so that I know where to dig.
Sorry for the confusion that there is not so much information, today there was not even time to dig deeper into the system logs.

Answer 1

Although a lot of time has passed, but I will write my answer, maybe it will be useful to someone. I struggled with this problem for a very long time until I found the cause, and the installed protection driver for the key - Sentinel Runtime - was to blame. After removing it, the network type began to switch without problems. It is removed through the standard uninstaller. How to combine this driver with the network did not understand, because. later we didn't need it.

Answer 2

If the computer just goes into a reboot without even asking for confirmation, then it is quite possible that you won’t be able to do without restoring Windows.
The nerves of the chief accountant will not solve anything here - the speed of solving the problem does not depend on them at all.
If you do not have the opportunity to transfer the chief accountant to another computer (usually 1C is quite easy to transfer, the office is easy to set up, documents, if they are organized on a network drive, and a small part of them on the desktop or personal folder are also transferred quickly), then immediately tell the chief accountant that manually recovering such errors is not regulated by the vendor, so no one can give a deadline for correction.
Therefore, "on time" and "very quickly" can only give instructions, and not execute them. Report the deadlines for solving those tasks in which you are sure.
Options for what to do
1. Look in the registry - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles, here you can change the network type
0 - Public Network (Public Network)
1 - Private Network (Private Network)
2 - Domain Network ( Domain Network)
Can give a ride. Perhaps a reboot is needed.
2. You can dig aside to remove / install network drivers, including the actual IP service in the settings of the network card.
3. Why change the network type at all? Set up access without changing the category.

Answer 3

The thing is that the desktop computer categorically refuses to share over the network, and creates a headache when trying to configure it.

This problem is not in the computer, but in the system administrator.

When you try to change the type of network from “public”, to “home” or “enterprise network”, the computer instantly goes into reboot.

Reboot is the presence of obvious problems - start with diagnostics.

На форумах также информация разнится - кто-то говорит, что проблема в оборудовании, кто-то жалуется на магический «сетевой вирус».

Без диагностики что еще можно посоветовать?

Завтра нужно будет своевременно, и очень быстро решить эту проблему,

Главбуху ставите какой-нибудь резервный комп на подмену, накатываете на него бэкап и пусть работает.
А проблемный - на диагностику.

Answer 4

Windows 10 автоматически становится ведущим(главным) в домене. Начните с его настройки сети. А 7-ку подключайте в уже существующий домен 10-ки. Уже потом расшаривайте принтер и папки на 7-ке.

Answer 5

ненужные оюновления, которые загружаются от сервисов Виндоус, я так думаю...