At the end of the section there seems to be alignment padding that can contain remnant values.

−

== Section D ==

+

== Section D - Volume information (block) ==

Section D contains one or more subsections. The number is (most likely) determined by the DWORD at file offset 0x0070. Each subsection refers to directories on an identified volume.

Section D contains one or more subsections. The number is (most likely) determined by the DWORD at file offset 0x0070. Each subsection refers to directories on an identified volume.

Line 220:

Line 263:

|}

|}

+

If all the executables and libraries referenced in the C section are from one single disk volume, there will be only one section in the D section. If multiple volumes are referenced by section C, section D will contain multiple sections. (A simple way to force this situation is to copy, say, NOTEPAD.EXE to a USB drive, and start it from that volume. The corresponding prefetch file will have one D header referring to, e.g. \DEVICE\HARDDISK1\DP(1)0-0+4 (the USB drive), and one to, e.g. \DEVICE\HARDDISKVOLUME1\ (where the .DLLs and other support files were found).

+

== See Also ==

+

* [[Prefetch]]

−

If all the executables and libraries referenced in the C section are from one single disk volume, there will be only one section in the D section. If multiple volumes are referenced by section C, section D will contain multiple sections. (A simple way to force this situation is to copy, say, NOTEPAD.EXE to a USB drive, and start it from that volume. The corresponding prefetch file will have one D header referring to, e.g. \DEVICE\HARDDISK1\DP(1)0-0+4 (the USB drive), and one to, e.g. \DEVICE\HARDDISKVOLUME1\ (where the .DLLs and other support files were found).

+

== External Links ==

Revision as of 13:39, 20 October 2013

Please help to improve this article by expanding it.
Further information might be found on the discussion page.

A Windows Prefetch file consists of one file header and multiple file sections with different content. Not all content has an obvious forensic value.

As far as have been possible to ascertain, there is no public description of the format. The description below has been synthesised from examination
of multiple prefetch files.

Section C

At the end of the section there seems to be alignment padding that can contain remnant values.

Section D - Volume information (block)

Section D contains one or more subsections. The number is (most likely) determined by the DWORD at file offset 0x0070. Each subsection refers to directories on an identified volume.

In this section, all offsets are assumed to be counted from the start of the D section.

Field

Offset

Length

Type

Notes

DH1

+0x0000

4

DWORD

Offset to volume string (Unicode, terminated by U+0000)

DH2

+0x0004

4

DWORD

Length of volume string (nr of characters, including terminating U+0000)

DH3

+0x0008

8

FTIME

(File time)

DH4

+0x0010

4

DWORD

Volume serial number of volume indicated by volume string

DH5

+0x0014

4

DWORD

? Offset to section DHS1

DH6

+0x0018

4

DWORD

? Length of section DHS1 (in bytes)

DH7

+0x001C

4

DWORD

? Offset to section DHS2

DH8

+0x0020

4

DWORD

? Nr of strings in section DHS2

?

+0x0024

?

?

? additional 28 bytes (includes one timestamp?)

If all the executables and libraries referenced in the C section are from one single disk volume, there will be only one section in the D section. If multiple volumes are referenced by section C, section D will contain multiple sections. (A simple way to force this situation is to copy, say, NOTEPAD.EXE to a USB drive, and start it from that volume. The corresponding prefetch file will have one D header referring to, e.g. \DEVICE\HARDDISK1\DP(1)0-0+4 (the USB drive), and one to, e.g. \DEVICE\HARDDISKVOLUME1\ (where the .DLLs and other support files were found).