4 ms·

Intel, AMD and Via microcode is being archived by CPUID, by the user community: https://www.win-raid.com/t3355f47-Intel-AMD-amp-VIA-CPU-Microcode-Repositories.

Intel, AMD and Via microcode is being archived by CPUID, by the user community: https://www.win-raid.com/t3355f47-Intel-AMD-amp-VIA-CPU-Microcode-Repositories.html https://www.win-raid.com/t3355f47-Intel-AMD-amp-VIA-CPU-Micr... "Collecting all available Production CPU microcodes is important for upgrading/downgrading purposes, for creating universal tools that can help people understand what microcode they use, for research on how the general technology works, for developers with no vendor representative who want to experiment on a given platform etc. Disclaimer: All the microcodes below come only from official BIOS/UEFI updates, Intel Linux Microcode Updates, Linux Distributions, Windows Updates etc which were provided and made public by various manufacturers! It is always advised to request and/or wait for your OEM/OS to release newer fixes. The microcodes are gathered and provided with the sole purpose of helping people who are out of other viable solutions. Thus, they can be extremely helpful to those who have major problems with their systems for which their manufacturer refuses to assist due to indifference and/or system age."

steve19 9y ago
I always assumed they were not just signed but encrypted, and padded to avoid meta analysis. Is that not the case?
- monocasa 9y ago
  This recent talk shows that AMD ucode wasn't signed or encrypted up until 2013, and they reverse engineered large portions of the structure. https://www.youtube.com/watch?v=lY5kucyhKFc https://www.youtube.com/watch?v=lY5kucyhKFc
chrisper 9y ago
For Windows there is also this: https://labs.vmware.com/flings/vmware-cpu-microcode-update-driver#summary https://labs.vmware.com/flings/vmware-cpu-microcode-update-d... I have never tried it though.
- fred_is_fred 9y ago
  Wouldn't a live CD/USB also work?
  - chrisper 9y ago
    I believe the one from my link is lost between reboots. Windows does not seem to deliver microcode fixes except for the Surface.
    - danieldk 9y ago
      The microcode update is always lost between reboots. This is e.g. why the Linux kernel can update the microcode during early boot. The only way to make microcode updates stick between reboots is with a BIOS/EFI firmware update (some vendors provide firmware updates with microcode updates.). Then the microcode update gets applied during every boot automatically.

steve19 9y ago

I always assumed they were not just signed but encrypted, and padded to avoid meta analysis. Is that not the case?

monocasa 9y ago
This recent talk shows that AMD ucode wasn't signed or encrypted up until 2013, and they reverse engineered large portions of the structure. https://www.youtube.com/watch?v=lY5kucyhKFc https://www.youtube.com/watch?v=lY5kucyhKFc

chrisper 9y ago

For Windows there is also this: https://labs.vmware.com/flings/vmware-cpu-microcode-update-driver#summary https://labs.vmware.com/flings/vmware-cpu-microcode-update-d... I have never tried it though.

fred_is_fred 9y ago
Wouldn't a live CD/USB also work?
- chrisper 9y ago
  I believe the one from my link is lost between reboots. Windows does not seem to deliver microcode fixes except for the Surface.
  - danieldk 9y ago
    The microcode update is always lost between reboots. This is e.g. why the Linux kernel can update the microcode during early boot. The only way to make microcode updates stick between reboots is with a BIOS/EFI firmware update (some vendors provide firmware updates with microcode updates.). Then the microcode update gets applied during every boot automatically.