Unable to start IIS (Unexpected error 0x8ffe2740)

When IIS is started, the 0x8ffe2740 error occurs because of other reasons.ProgramIf port 80 is used, you can change the default port of IIS to a value greater than 80. After the port is successfully started, it is changed back to 80. If the port is started again, no error occurs. If the port is 500 again, reinstall IIS to solve the problem.

Cause: Unexpected error 0x8ffe2740
Cause:
This situation may occur if a port conflict exists in the system. by default, IIS uses port 80 for HTTP Communication. if the application except IIS is running and port 80 is being used on the same IP address, you may also receive this error message when trying to start the website using IIS manager.Solution
To solve this problem, you can perform any of the following operations:
"In IIS manager, change the website binding port to a port other than port 80.
"Stop the application that is using port 80, and then start the website from IIS manager.
More information
You can use third-party tools such as tcpview or fport to determine other applications that are using port 80.

Method 1:
IIS Admin Service

In start-run, enter services. MSC
Open the Service Manager (you can also find it in the management tool)
Locate the IIS Admin Service. if the service is not started, start it.

Method 2
Change port 80

If you do not know what program occupies port 80, use tcpview or fport to check what program. Turns out to be a Trojan!
If not, change the port.

Method 3:
After MySQL is disabled, IIS cannot be used.
I used a firewall. After I disabled it, I cannot use IIS.
An unexpected error occurs: 0x8ffe2740. After in-depth analysis, although the previous practice was successful, IIS stop still occurs after each computer restart.

To find out whether the Administrator tools> service item was read this time
Use fport to find out the program svchost.exe that occupies port 80 and the PID of the program.
PID process port proto path
1396 svchost-> 80 TCP c: \ windows \ system32 \ svchost.exe

Although
The task manager can delete the svchost.exe file directly. However, after the next restart, the same situation will occur.
Svchost.exe will be used after the restart. What is it? Check the service and finally lock the target on mysee2_runtime.
[C: \ windows \ system32 \ svchost.exe-K
Mysee2] after the service is stopped, IIS can be restarted. To avoid this IIS problem, you can also use mysee. You can only change this service to manual. Watch the streaming media of mysee
It's really troublesome.

The problem persists after the restart.