You're right, but I thought that windows defender would still be active during AV installation and maybe it would hinder the process.
Yes, I've found that a data DVD can burn almost twice as fast with a third party antivirus compared with Windows Defender. The Defender just can't keep up with the rate at which the Burner wants to write.
If I'm not wrong, he wanted to say that Windows Defender slowed down the disc writing process while other 3rd party antivirus didn't affect the disc writing task and even gave him double speed.
After some research, most older ASUS board+Intel with VT-d enabled won't update/even boot (like mine). If you use virtualization, BE WARNED!
Correct. A few weeks ago I was burning data DVD and was surprised how long it was taking. I remembered I'd recently removed the antivirus, so installed one again and tried again. The speed was immediately back to normal, and processor use was lower too.
Define normal, facts not feelings please... What were the speed rates when using the 3rd party AV and the standard Windows defender, what dvd writing software was used, and what speed settings were applied?
The burning software was Nero Burning Rom, burning at max speed with 16x DVDs. The disks hold a few thousand assorted utility files that I take round on DVD with me. Generally takes about 10 minutes to burn and verify one. Without 3rd party antivirus the burning process was struggling to keep the buffer filled and kept pausing. I didn't time it, but it was closer to 20 minutes. The Windows Defender process was showing high processor use during the burn. Repeating after installing a 3rd party antivirus (360 Security in this case) showed much lower overall processor use, Nero maintained a full buffer throughout and it was back to around 10 minutes.
U are aware that burning prosses does take up a lot of CPU power. I don't think antivirus plays any role in this.
Considering your usual sketchy responses, I'm hardly surprised your watered-down definition of "testing", and then using it to validate your ineptitude. Only in this venue would anyone ever consider what you do as developer testing. Then again, this is the same person who said Pro for Workstations was equivalent to Enterprise, posted screenshots of incorporating OOBE packages into an offline image, recommended that people use Microsoft's default setup disk layout for "proper" disk partitioning, etc.
I found a difference between 17134.1 and 17134.5. When scanning with WUMT against Windows Update, in 17134.1 it shows as installed Feature update to Windows 10, version 1803 under Upgrades. With the patch, 17134.5 does not show this entry. It may be the recognition that IP has passed the threshold to become RTM. We will understand more soon. Next Patch Tuesday is in few days from now.