Tag Archives: upgrade error

Windows 11 Unsupported CPU

Posted on by
Reply

Unsupported CPU KB ID 0001878

Problem

I needed to upgrade a Windows 11 VM from 21H2 to 23H2, as is recommended I installed the PC Health Check, I was surprised to see this error.

The processor isn’t currently supported for Windows 11.
More about supported CPUs
Processor Intel Xeon CPU E5-2650 v3 @ 2.4GHz

I say surprised, because although this was a VMware virtual machine it was ultimately on a HPE DL360 Gen 9 – which is getting on, but is in no way ancient.

Solution : Windows 11 Unsupported CPU

I’ve written before about to how to bypass the lack of a TPM, but you can also get Windows 11 to bypass the processor check also.

Launch the registry editor (regedit) and navigate to the following location

[box]

HKEY_LOCAL_MACHINE > SYSTEM > Setup > MoSetup

[/box]

Note: On my 21H2 VM the MoSetup Key did not exist, so I had to create that key first!

Create a new 32 bit DWORD value called AllowUpgradesWithUnsupportedTPMOrCPU and set it value to 1 (one).

You should now be able to perform the upgrade without error.

Start and end results of winver prove the upgrade was then successful.

Related Articles, References, Credits, or External Links

NA

Exchange Update / Install Error: The Error Code Is 8224

Posted on by
Reply

KB ID 0001451

Problem

I saw this error while attempting to install an update on Exchange 2010, but it can be seen on all flavours of Exchange. This is the ‘gist’ of the error;

[box]

Organization Preparation
Failed

Error:
The following error was generated when "$error.Clear(); 
	install-ExchangeSchema -LdapFileName ($roleInstallPath + "Setup\Data\"+$RoleSchemaPrefix + "schema0.ldf")

" was run: "There was an error while running 'ldifde.exe' to import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\PostExchange2003_schema0.ldf'. The error code is: 8224. More details can be found in the error file: 'C:\Users\{Username}\AppData\Local\Temp\ldif.err'".

There was an error while running 'ldifde.exe' to import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\PostExchange2003_schema0.ldf'. The error code is: 8224. More details can be found in the error file: 'C:\Users\{Username}\AppData\Local\Temp\ldif.err'
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex88D115&l=0&cl=cp

[/box]

Solution

This was an easy one to sort out, on one of your domain controllers open “Active Directory Sites and Services”, expand all the sites and look at the server names. In my case there was an old DC in the list (these are usually easy to spot as you cant ‘expand’ them), i.e.theres no NTDS settings below them.

Simply right click the offending server and delete it, then either force domain replication, or wait a while.

Related Articles, References, Credits, or External Links

NA

Webmin – Upgrade Error – ‘Perl (Net::SSLeay) is needed’

Posted on by

KB ID 0001100 

Problem

I like to keep my CentOS server updated as much as I can, but the last couple of times I’ve gone to run the upgrade of the Webmin console, I’ve got this;

error: Failed dependencies:

perl(Net::SSLeay) is needed by webmin (version)

Solution

1. As error messages go this is not a bad one, it obviously needs perl installing. So SSH into the server and execute the following command;

[box]yum -y install perl perl-Net-SSLeay openssl perl-IO-Tty[/box]

2. On successful completion, go back to Webmin and attempt the upgrade again.

Related Articles, References, Credits, or External Links

NA