Skip to content

Fix architecture typo blocking scheduled_tasks on 32-bit images - #2016

Merged
ikelos merged 1 commit into
volatilityfoundation:developfrom
mmadersbacher:fix/scheduled-tasks-arch-typo
Aug 19, 2026
Merged

Fix architecture typo blocking scheduled_tasks on 32-bit images#2016
ikelos merged 1 commit into
volatilityfoundation:developfrom
mmadersbacher:fix/scheduled-tasks-arch-typo

Conversation

@mmadersbacher

Copy link
Copy Markdown
Contributor

ScheduledTasks.get_requirements() asks for architectures=["Intel33", "Intel64"]. There is no Intel33. Intel layers only ever report Intel32 or Intel64 (framework/layers/intel.py:43 and :478), so on a 32-bit image the kernel requirement can never be satisfied and the plugin aborts with an error that points at the layer instead of the architecture:

Unsatisfied requirement plugins.ScheduledTasks.kernel.layer_name

The deprecated windows.scheduled_tasks.ScheduledTasks alias is affected the same way.

Checked against both images from the test workflow:

image before after
win-xp-laptop-2005-06-25.img (32-bit) rc=1, unsatisfied requirement rc=0
win-10_19041-2025_03.dmp (64-bit) rc=0, 330 rows rc=0, 330 rows

ruff check and ruff format --check clean. test/plugins/windows/windows.py 63 passed, test/plugins/windows/test_scheduled_tasks.py 3 passed.

The kernel requirement listed "Intel33". Intel layers only ever report
Intel32 or Intel64, so on a 32-bit image the requirement could never be
satisfied and the plugin aborted with a misleading "Unsatisfied
requirement ... kernel.layer_name" instead of running.

@ikelos ikelos left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good work spotting this! 5:D

@ikelos
ikelos merged commit 9e49316 into volatilityfoundation:develop Aug 19, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants