That was just the .job name, the dastardly deed is the string/command inside and the urqPgDUm.dll would probably inject .exe files when run with code to do its bidding. Keep this task disabled. also task scheduler disabled, if there are no schedules that you created in there.
Upload that urqPgDUm.dll file to virustotal (VT) as the above link to VT and report the results.
Depending on the results of the VT results, if multiple scanners detect it as malicious, likely, then we would delete the task, but first report the findings. As a temporary measure you could rename the urqPgDUm.dll file to something like XXXurqPgDUm.dll, so even if that task manager task ran the file it would be trying to run wouldn't exist as we renamed it.
I have no idea what 0X103 is, hopefully an error code that it didn't work, but that is optomistic speculation on my part. The creator is whatever account was logged on as malware inherits your permissions.
Personally I would say Bonjour is a minor issue, which you can get to once you are sure your system is clean, something created that .job and it wasn't you.
Work through Tech's steps 1 - 3, on step 3 only download, install, update and run SAS and MBAM (the first two on that line) and report the findings - preferably run them from safe mode, it makes dealing with any infections found more effective.
