Essexboy is on holiday now as his last post indicates.
In certain locations the kernel32.dll is a system file, this is also an important system file. The problem being this file is a bit weird as it is a 32bit dll that is why it is nit the syswow64 folder so that 32bit applications can use it.
When executing 32-bit applications, WoW64 transparently redirects 32-bit DLLs to %SystemRoot%\SysWOW64, which contains 32-bit libraries and executables. ...
For some reason the emulation function in the scan considered this infected, I don't know what this reason is.
A bit of speculation on my part after information from another source - In this case if you had ignored the detection and rebooted, then the copy of the file in the syswow64 folder would have been recreated and may not be subsequently detected. So the detections on files in the syswow64 folder are a bit weird as they aren't actually the original file but a copy of it. So I don't know why the emulation element found it strange enough to flag it.
But I don't know what would happen with the other occurrences, which is why following that guide was advised by essexboy.