I’m trying to export NVRAM settings via SCEWIN/AMISCE on a Fujitsu D3221-B1
board (Fujitsu D3221-B1x, Terra PC, Intel i7-4790, socket LGA1150),
but no version of the utility works.
Board & firmware details:
Board: D3221-B1x
BIOS Vendor: American Megatrends (AMI Aptio Setup Utility)
Core Version: 4.6.5.4
Tested on BIOS revisions R1.34.0 (2015) and R1.47.0 (2019, latest official)
Same results on BOTH firmware revisions (R1.34.0 and R1.47.0) —
updating the firmware did not change anything
Secure Boot: disabled (confirmed “Not Active” in BIOS)
Windows testsigning: enabled
Memory Integrity/Core Isolation: disabled
Running as Administrator, Windows 10
I have the .rom/.bup image of the official R1.47.0 firmware and I’m willing
to check it in UEFITool. Is there a known way to check whether the SCE/HII
driver module is present or missing/disabled in this specific Fujitsu build?
Has anyone dealt with Fujitsu D-series boards blocking SCE access?
Follow-up: I checked the R1.47.0 firmware image in UEFITool (NE alpha).
Text search results:
“AMISCE” - could not be found
“SCEDriver” - could not be found
“HII” - multiple matches, including several inside
AMITSE/…/MiniSetupResourceSection (offsets 1693h, 16B6h, 16DDh, 1704h)
So it looks like the HII resource data itself is present (via AMITSE -
AMI Text Setup Engine), but there’s no dedicated AMISCE/SCE driver module
in this build at all - not disabled, just not included.
Is it feasible to add a compatible AMISCE/SCE driver module from another
AMI Aptio IV (core 4.6.5.4) firmware into this image? If so:
Does anyone have a donor firmware with a compatible module I could
reference or extract from?
What needs to be checked for compatibility (Depex dependencies, GUID,
core version match)?
Given this board doesn’t support Windows-based flashing of a modified
image (signature/integrity checks), would this require an external
programmer (CH341A) to flash?
I understand this is a non-trivial modification with real bricking risk,
so I’d rather get guidance from people experienced with Aptio IV modding
before attempting anything.
I downloaded D3221-B1.rom, and I think the error appears due to the absence of SmiVariable driver. It utilizes smi_cmd port defined in FADT acpi table to set efi variables from OS (and not only). So if there’s no driver, it makes sense that SCEWIN says the BIOS is incompatible.
That would make sense and would also explain why /d gives:
ERROR:4 - Retrieving HII Database
ERROR:4 - BIOS not compatible
I checked the firmware in UEFITool and couldn’t find AMISCE or SCEDriver, although HII resources are present inside AMITSE/MiniSetupResourceSection.
I haven’t specifically checked for SmiVariable yet. What would be the best way to verify whether the SmiVariable driver and the required SMI mechanism are present in this D3221-B1 image?
Idk what other SMI mechanisms are. Cant help you with this.
IMO, your best bet to access Admin menu in Advanced page is something else but SCEWIN.
I have one Aptio IV device at hand, so I’ll try to come up with something, which won’t require image modding and chip programming.
I plan to tackle this tomorrow and write up the results unless, of course, you find a solution before I do.
Here ItsCaff.zip (552.0 KB)
Copy the contents to a FAT formatted usb, and boot from it. Boot option filter option in bios should remain at “UEFI and Legacy” and Secure Boot - Disabled.
Once booted, wait several seconds and it should display SetVariable… Success or other error code. Then you may reboot.
I tested the script on my pc, but with a different variable (SystemAccess) and it worked.