I think to sort this through, a recap is in order
The issue: Slow startup & Errors/Warnings in the event log
Maxie suggested uninstalling Bonjour & Apple Product Updater
-> You disabled the Bonjour Service, saw no change so you re-enabled it
:note: You can safely uninstall both - please do
You noted that reading through some event logs that Computer Browser depends on the Server Service which failed to start due to a dependency service failure to start. You changed some service (not sure which) from manual to automatic start, rebooted and saw fewer errors in event logs. The slow startup issue was still present.
:note: Are the Computer Browser and Server services running now? If not, look at the Server service - > Dependencies tab and see which component is failing. Post a screenshot of the Server service - > Dependencies tab
Maxie suggested a MS Fixit for WMI 10, but redirected you to msconfig to disable Adobe Arm.
:warn: No mention of msconfig startup changes
You couldn't find the MS Fixit and found a 82579v driver using the free Driver Genius. When you tried to install the driver, it said you had to uninstall the previous version of the driver.
:note: Never use 3rd party drivers - ALWAYS get a driver from the OEM site! No harm, no foul as you did not install that driver.
Maxie confirmed that it was not a good driver and pointed you to the Mobo's website.
I suggested that you create system image. then I wanted to see if IPv4 or IPv6 took precedence on your machine. I asked for the event logs under performance. I suggested the clean startup tutorial and provided a link to the WMI 10 MS Fixit. I asked for an ipconfig /all, requested the current version of the installed driver, and I provided a link to the Asus download for the 82579v driver noting the additional download stated on the Asus download reference.
:note: You had an image, but would create a fresh one. Your system prefers IPv4 and does not support IPv6. There were 17 pages of Event log entries (errors / warnings) posted later. WMI 10 MS Fixit will run later. ipconfig output posted. Current driver version is 11.8.74.0. You noted that Bitdefender was flagged as a slow startup item in the logs - this is fairly common with AV apps (27 seconds does seem long though - perhaps a configuration change might speed it up - not sure... back burner for now). You waited for a response on your feedback before downloading the Asus driver. You also noted that you recalled previously having both IPv4 & IPv6
:warn: No mention of following the tutorial:
Troubleshoot Application Conflicts by Performing a Clean Startup. This addresses the issue directly and needs to be completed.
:warn: The WMI 10 MS Fixit is not critical, but I'd like you to run it so that I can check it as done - thanks.
Maxie confirmed the Asus driver as a good choice and suggested removing Bitdefender from your startup.
:warn: No mention of msconfig startup changes
I reviewed what you posted, commented and had more to read. I suggested the SevenForums Diagnostic tool and the System File Checker to help this side of your monitor see what you see and to verify the system files.
:warn: No mention of the SevenForums Diagnostic tool and no output to read
PBCopter confirmed that the e1cexpress error was a timeout issue and suggested a workaround.
You posted the 17 pages of event logs from performance.
This is where things get a bit off track.
I'm not sure why you were in Command Prompt. Could you point me to the place where you were told to launch a Command? I know that the SFC tutorial needs an elevated Command, but do any other instructions (driver, NVM utility) require a Command prompt?
You chose to use the Global (DLM) link on Asus to download the driver. I'm not familiar with how that's all tied together and I should have pointed you to the Global (without DLM) download link. I think it would be easier if you download the driver again using the Global link (middle one).
:warn: Download the NVM utility first and run it. It might not have any work to do, but you won't know that until you run it.
:warn: Then install the 82579v driver second
maxie pointed you to the SFC tutorial again
You were still working in Command prompt trying to install the driver and having some difficulty. You asked about SFC (scan or verify). You also commented on the status of the Ethernet connection - it is marked unplugged.
:note: No mention if you applied PBCopter's configuration change - please do make the change.
:warn: This throws a stumble onto the path we were on, doesn't it! The device is not being used, yet it migh still contribute to the slow startup.
maxie suggested placing 82579vskuw64e.exe on your desktop for easy access. And confirmed the scan function of SFC.
You ran SFC with /verifyonly which returned
Windows Resource Protection did not find any integrity violations. You had more questions about Command prompt. This is some fairly technical stuff we're asking you to do, don't worry if you have questions.
maxie 'explained' the arrows, but I'm not sure that helped

. then he asked if your internet connection was secure or not.
maxie suggested that a hardwired connection might solve the issue.
you were still having Command difficulties. You seemed to be stuck on running things in Command - try this: Forget about Command Prompt unless explicitly instructed to launch one.
maxie shrugged
maxie requested a speedtest and reiterated that you might get better throughput using a hardwired connection.
I played catchup which prompted this recap. I will post a todo lit next, then I'll go back to reading the performance logs.
You can work off the todo list in my next post - this is just a recap.
Bill
.