Blog9 min read
Bits-Client Event IDs: What Each One Proves
The Microsoft-Windows-Bits-Client/Operational log: events 3, 4, 5, 59, 60, 61 and 64, what they record, typical sequences, what they prove and what they leave out.
TL;DR. Microsoft-Windows-Bits-Client/Operational records BITS activity as the client sees it. Event 3 marks a new job, with its name and owner and, on recent builds, the process that created it. 59 and 60 bracket a transfer and carry the URL; 61 takes the place of 60 when the transfer stops with an error; 4 marks completion. 64 is the only one that names a notify program, and only when BITS fails to launch it. A clean download reads 3, 59, 60, 4; Mandiant's KEGTAP case reads 3, 61, 64. Microsoft publishes no reference for these IDs, so their meanings come from tests and case write-ups, and some, such as 16403, are still disputed. No event gives the local destination path: that is in the job database. BITS Parser reads this log as well as the database.
The channel
| Item | Value |
|---|---|
| Channel | Microsoft-Windows-Bits-Client/Operational |
| File | C:\Windows\System32\winevt\Logs\Microsoft-Windows-Bits-Client%4Operational.evtx |
| State | Populated by default in the cases and tests cited here, on Windows 7 and 10 |
| Retention | Rolls over at the channel's maximum size; can be cleared, as Xavier Mertens notes in his ISC diary |
BITS also has an analytic channel, which bitsadmin /util /enableanalyticchannel turns on. Analytic channels are off by default, and nothing on this page relies on it.
The IDs at a glance
| ID | Meaning | Key data | Sources |
|---|---|---|---|
| 3 | The BITS service created a new job | Job name, job ID, owner; on recent builds the creating process | Mandiant, JPCERT, Nardella |
| 59 | BITS started a transfer | Job name, URL, sizes | JPCERT, Nardella, Matt Green's Velociraptor artifact |
| 60 | BITS stopped a transfer | Job name, URL, status code (0x0 on success) | JPCERT, Nardella |
| 61 | BITS stopped a transfer with an error (Warning) | Job name, URL, status code | Mandiant, Nardella |
| 4 | The transfer job completed | Job ID, owner, user, file count, bytes transferred | JPCERT, Nardella |
| 5 | Job cancelled | LogRhythm's event list only | |
| 64 | A notify program could not be launched (Warning) | Job name, program path, URL, error code | Mandiant |
| 16403 | Disputed | See below |
The main sources: Mandiant's KEGTAP case, JPCERT's tool analysis sheet, Roberto Nardella's SANS paper, LogRhythm's Bits-Client message list and Matt Green's Windows.EventLogs.Bitsadmin artifact.
Event 3: a job is created
The message starts "The BITS service created a new job" and gives the job name and owner; Mandiant's figure shows the name "System update". JPCERT's sheet adds the job ID and the path of the creating process, powershell.exe in its test. Other write-ups use that field to tell bitsadmin.exe from PowerShell. The Windows Forensics BITS page says the process appears "on some versions"; older builds may not have it.
- Proves: a job with this name was created at this time, owned by this account, and, when the field is there, at the request of this program. Any program can ask, including malware calling the COM interface directly, so the field is often the only trace of the real client.
- Does not prove: that anything was transferred. A job created with
bitsadmin /createstays suspended until it is resumed.
Events 59, 60 and 61: transfers
- 59 opens a transfer. JPCERT's message reads "BITS started the BITS Transfer transfer job associated with the URL" followed by the URL;
BITS Transferis the job name there, the default name ofStart-BitsTransfer. Matt Green's artifact reads these fields from it:transferId,name,id,url,peer,fileTime,fileLength,bytesTotal,bytesTransferredandbytesTransferredFromPeer. Nardella notes thatbytesTransferredis zero at this point. WhatfileTimemeasures is not documented. - 60 closes it, with a status code. JPCERT's test shows
0x0for success. - 61 closes it with an error. Nardella found that an interrupted download writes 61 instead of 60. Mandiant shows it as a Warning: "BITS stopped transferring the System update transfer job", with the URL and the status code
2147954429.
The status codes are HRESULTs printed in decimal. Convert them to hexadecimal before you look them up: 2147954429 is 0x80072EFD, which wraps WinINet error 12029, ERROR_INTERNET_CANNOT_CONNECT. Mandiant does not decode it; the conversion is ours.
- Proves: BITS tried to transfer that URL for that job at that time, and how the attempt ended.
- Does not prove: where the file was written or what it was renamed to. Nardella points out that the event data has neither. Join the URL to the file record in the job database for the destination and temporary paths.
Event 4: completion
JPCERT's event 4 holds the job ID, the user, the owner and the file count; in Nardella's tests, bytesTransferred equals the size of the downloaded file.
Sources describe it as the completion of the job. Whether it is written when the last byte arrives or when the client calls Complete is not documented; in the tests cited, the client completed the job at once, so the two coincide. A job left in the transferred state on purpose, as in BITS persistence, may never produce it.
Event 5: cancellation
LogRhythm's list names event 5 "Job Cancelled". None of the other sources discusses it. Treat it as a lead: a cancelled job leaves the queue, so carved records and the file system are what remain.
Event 64: a notify program could not be launched
Mandiant quotes it in full. The message names the job, the program BITS was configured to launch, and the URL whose transfer triggered it, gives an error code, and says BITS "will continue trying to launch the program periodically". In the KEGTAP case the code was 2147942402, which is 0x80070002: file not found, as an HRESULT.
- Proves: the job had a notify command line, with that program path, and BITS tried to run it and failed.
- Does not prove: that the program ever ran. No source we found documents an event for a successful launch. For that, look for a process whose parent is
svchost.exe -k netsvcs -p -s BITS, as Atomic Red Team shows, in Security 4688 or Sysmon 1, and for the program's Prefetch file.
Event 64 is the only event that shows a notify command line. Its absence means nothing: a program that starts cleanly leaves no trace in this log.
Event 16403 and the rest
Event 16403 is not settled. LogRhythm lists it as "CCM Message Upload", which points to Configuration Manager, and other write-ups describe it as a job or transfer event with details of their own. Look at what it holds on your build before using it.
LogRhythm's list also names 203 and 204 (job credentials accepted or rejected), 209 (high performance property for a job), 302 (BITS service started), 306 (job list loaded from disk), and 310 and 311 (peer errors). Events 302 and 306, if present, help place service restarts around a job's history.
Typical sequences
| Scenario | Sequence | Source |
|---|---|---|
Download that succeeds (bitsadmin /transfer, Start-BitsTransfer) | 3, 59, 60 with 0x0, 4 | Nardella, JPCERT |
| Upload that succeeds | 3, 59, 60, 4 | Nardella: the same sequence as a download |
| Download interrupted | 3, 59, 61 | Nardella |
| Notify program that cannot be launched | 3, 61, 64 | Mandiant's KEGTAP case |
Reading the KEGTAP events
In 2020, Mandiant responded to Ryuk operators who used the KEGTAP backdoor. On one workstation, no usual persistence was found, but the Bits-Client log held three events:
- Event 3: a new job named "System update", with the owner redacted.
- Event 61: the job stopped transferring
http://127.0.0.1/tst/56/, status0x80072EFD, cannot connect, which fits a URL on localhost with nothing listening. - Event 64: BITS could not launch
mail.exe, in the user'sINetCachefolder, after the transfer ofhttp://127.0.0.1/tst/12/, error file not found.
The job database confirmed the rest: a download job, state queued, with mail.exe as notify command. The pattern is a URL designed to fail, so that the error state launches the program. The article does not explain why event 61 and the database show /tst/56/ while event 64 shows /tst/12/; report such differences as they are.
What the log does not tell you
- the local destination path and final name of a file;
- the notify command line of a job whose program launches without error;
- retry settings and other job properties;
- the command line that created the job, which comes from process creation logs or PowerShell logging;
- anything older than the channel's rollover.
Joining events to the job database
| Key | In the log | In the database |
|---|---|---|
| Job name | Events 3, 59, 60, 61, 64 | Job record. Names need not be unique, as Microsoft's bitsadmin page warns |
| Job ID | Events 3 and 4 (JPCERT); an id field in 59, per Matt Green's artifact | Job GUID. Check on your build that the id in 59 is the job GUID before joining on it |
| URL | Events 59, 60, 61, 64 | File record source URL |
| Time | Event 3 time | Job creation time |
Collecting the log
On a live system, wevtutil epl Microsoft-Windows-Bits-Client/Operational <file>.evtx exports the channel; on a disk image, copy the .evtx file. Both are covered with the database files in collecting BITS evidence.
FAQ
Which event ID shows a BITS job being created?
Event 3 in Microsoft-Windows-Bits-Client/Operational: the BITS service created a new job. It names the job and its owner, and on recent Windows builds also the path of the process that created it, such as bitsadmin.exe or powershell.exe.
Which BITS events contain the URL?
Events 59 (transfer started), 60 (transfer stopped) and 61 (transfer stopped with an error) name the URL. Event 64 names the URL of the transfer whose notify program BITS could not launch. None of them gives the local destination path.
What does Bits-Client event 64 mean?
BITS was configured to launch a program after a job's transfer, and the launch failed. The message names the job, the program, the URL and the error, and says BITS will keep trying. It proves that the job had a notify command line, and it is only written when the launch fails.
What is Bits-Client event 16403?
Public sources disagree. LogRhythm's documentation lists it as a CCM message upload, while other write-ups describe it as a job or transfer event. Check what it holds on your own Windows build before relying on it.
Related articles
Frequently asked questions
Which event ID shows a BITS job being created?
Event 3 in Microsoft-Windows-Bits-Client/Operational: the BITS service created a new job. It names the job and its owner, and on recent Windows builds also the path of the process that created it, such as bitsadmin.exe or powershell.exe.
Which BITS events contain the URL?
Events 59 (transfer started), 60 (transfer stopped) and 61 (transfer stopped with an error) name the URL. Event 64 names the URL of the transfer whose notify program BITS could not launch. None of them gives the local destination path.
What does Bits-Client event 64 mean?
BITS was configured to launch a program after a job's transfer, and the launch failed. The message names the job, the program, the URL and the error, and says BITS will keep trying. It proves that the job had a notify command line, and it is only written when the launch fails.
What is Bits-Client event 16403?
Public sources disagree. LogRhythm's documentation lists it as a CCM message upload, while other write-ups describe it as a job or transfer event. Check what it holds on your own Windows build before relying on it.