Installing Windows 11 by removing appraiserres.dll file

Bree · May 1, 2022

MichaelMuh said:
I did not mean 'Deleting appraiserres.dll from C:\$Windows.~BT\Sources', I meant removing the appraiserres.dll file from the Sources Folder of the Install Media USB Stick

I was pointing out that a clean install isn't the only time appraiserres.dll is used, it also plays a part in a Feature Update through Windows Update. And in that instance it has to be replaced, not deleted.

spapakons · May 2, 2022

It is very tricky to use Windows Update to install feature upgrades. I would simply download the new ISO from UPP and do the same hack (delete or replace the appraiserres.dll file). I am running the standard Windows 11 release, so Windows Update doesn't check compatibility when installing updates. I am sure it will when trying to upgrade to 22H2 in October, but until then no worries. Then I will download the 22H2 ISO and do the hack to upgrade.

Bree · May 2, 2022

spapakons said:
It is very tricky to use Windows Update to install feature upgrades. I would simply download the new ISO from UPP and do the same hack (delete or replace the appraiserres.dll file). I am running the standard Windows 11 release, so Windows Update doesn't check compatibility when installing updates. I am sure it will when trying to upgrade to 22H2 in October, but until then no worries. Then I will download the 22H2 ISO and do the hack to upgrade.

My Lenovo Yoga 11e 2-in-1 laptop has a weird touchscreen driver, the touchscreen is not recognised by a clean install (of Windows 10 or 11) and the driver is tricky to install, even from the OEM support site. Google is full of questions about it.....

Google search: Lenovo Yoga 11e touchscreen not working

A Feature Update through Windows Update does however preserve my installed driver, so it is my preferred method for this particular machine.

My experience is that after Windows Update has downloaded the upgrade and starts to install a window like the one seen with a clean install pops up to tell you why it doesn't meet the requirements. Windows Update then shows a failed update with a Retry button. At this point you can replace C:\$Windows.~BT\sources\appraiserres.dll with a zero length dummy file (make a New Text Document, rename it, and copy to Sources). Then press Retry in Windows Update and the upgrade will complete the install. Just deleting appraiserres.dll is not enough, it will cause the install to fail again.

spapakons · May 2, 2022

Good trick. I will try it if needed. Thanks. As for the touch driver, download the chipset (platform) drivers directly from Lenovo and install it with right-click, Run as Administrator. It will restore touch functionality and anything else lost by inappropriate drivers.

Bree · May 5, 2022

Bree said:
At this point you can replace C:\$Windows.~BT\sources\appraiserres.dll with a zero length dummy file (make a New Text Document, rename it, and copy to Sources).

There has been a new feature update for the Dev/Beta channel. and I've had a chance to experiment a bit. I've found that the replacement appraiserres.dll must be a zero length file for this to work reliably.

ThrashZone · May 5, 2022

Bree said:
There has been a new feature update for the Dev/Beta channel. and I've had a chance to experiment a bit. I've found that the replacement appraiserres.dll must be a zero length file for this to work reliably.

Hi,
What the hell does that even mean :boom:

Bree · May 5, 2022

ThrashZone said:
What the hell does that even mean

Exactly what it says, a file that has zero bytes in it.

spapakons · May 6, 2022

So the file must be present, but instead of the real file you save an empty document in Notepad named appraiserres.dll (make sure there is no .txt extension in the end).

Bree · May 6, 2022

spapakons said:
So the file must be present, but instead of the real file you save an empty document in Notepad named appraiserres.dll (make sure there is no .txt extension in the end).

Yes exactly that. But you don't need to use Notepad, just right-click and make a New Text Document then rename it.

riverlandsmj · Apr 10, 2023

spapakons said:
Download latest Windows 11 ISO and mount it (open with Windows Explorer). It will create a virtual DVD drive where you see the contents of the ISO. Run Setup, it will count to 100% and then show the first screen. Before proceeding open This PC and open C: then open the Windows.~BT folder, then the sources folder. Delete the file appreserres.dll Now check had been bypassed and you can proceed with the upgrade.

If you want to format and do a clean installation instead, the easiest way is to create a hybrid installation media. This is the same as a Windows 10 USB Flash drive, but with a specific file replaced. Download the Windows 10 ISO and create a USB Flash drive. Now download the Windows 11 ISO (make sure you download the same language), mount it and copy the file install.wim (or install.esd) from the sources folder into the sources folder of the USB Flash drive replacing it. Boot the target computer with this hybrid USB Flash drive. There will be no compatibility check, just proceed with the installation.

Last week I upgraded my unsupported HP8200 desktop from Windows 10 using the current Windows 11 ISO. I did have to put a zero-length dummy appraserres.dll file in the Windows.~BT\sources folder for the install to proceed. I can also confirm that the hybrid USB stick worked perfectly on a 13 year old HP laptop that spectacularly failed the official UEFI, TPM and CPU requirements. Thanks to all who posted these helpful tips.

idgat · Apr 10, 2023

I can't help but wonder why everyone wants to try and re-invent the wheel ... Rufus has already done it

Download the Win 11 ISO
Download Rufus
Create a boot USB with Rufus using the option to bypass all Microsoft's ersatz security requirements.

Done. Boot from the USB and install Windows 11 on whatever you like (Anyone tried it on an Amstrad 128 ....

?)

Stigg · Apr 10, 2023

I could be wrong, but I thought I read about some issues people were experiencing with Windows 11 running on unsupported hardware due to a Windows update.

idgat · Apr 10, 2023

Stigg said:
I could be wrong, but I thought I read about some issues people were experiencing with Windows 11 running on unsupported hardware due to a Windows update.

Not here. Multiple devices involved, no problems.

There was some rumours that MS were going to watermark the desktop at some future update, but within hours of that rumour bubbling, hacks/fixes/workarounds abounded.

EDIT There may always be some risk, depending on the hardware. In most cases of problems, it involves self-built devices using cheap obscure brand hardware from some nefarious source ... that probably wasn't going to work anyway.

Stigg · Apr 10, 2023

idgat said:
Not here. Multiple devices involved, no problems.

There was some rumours that MS were going to watermark the desktop at some future update, but within hours of that rumour bubbling, hacks/fixes/workarounds abounded.

EDIT There may always be some risk, depending on the hardware. In most cases of problems, it involves self-built devices using cheap obscure brand hardware from some nefarious source ... that probably wasn't going to work anyway.

So, is there a watermark on the desktop now unless you apply a fix?

idgat · Apr 10, 2023

Stigg said:
So, is there a watermark on the desktop now unless you apply a fix?

Nary a trace down here. It could be a geo thing, though .....

Try3 · Apr 10, 2023

idgat said:
I can't help but wonder why everyone wants to try and re-invent the wheel ... Rufus has already done it

I can't help but wonder why Rufus wants to try to re-invent the wheel when we've already done it

Denis

idgat · Apr 10, 2023

Try3 said:
I can't help but wonder why Rufus wants to try to re-invent the wheel when we've already done it

Denis

Which is the chicken, and which is the egg ?

Stigg · Apr 10, 2023

idgat said:
Which is the chicken, and which is the egg ?

Which is the quickest and easiest?

spapakons · Apr 10, 2023

No there is no watermark. Microsoft simply doesn't offer you upgrade to the next version. All of us with the original 21H2 version we weren't offered to upgrade to current 22H2 version via Windows Update. All other updates download and install as if our computers were compliant. The issues are related to Windows Update replacing working drivers or incompatibilities between new features and customization software such as Explorer Patcher or other. Similar to Windows 10 issues. No we are not trying to reinvent the wheel. I am using a hybrid Windows 10/11 USB flash drive that I have added some utilities and drivers. If I was using Rufus I would have to wipe it and create it again for the next version, say 23H2. Not really convenient. I use a hybrid drive so I can just replace the 22H2 install.esd file with the respective file from 23H2 ISO. This way I will be able to install the newer version without wiping the entire USB flash drive. I did exactly that to change my USB from 21H2 to 22H2.

blackhole · May 8, 2023

Bree said:
I'm running the latest Dev build of Windows 11 on an unsupported laptop. There are frequent upgrades to the next build through Windows Update, aka a Feature Update. This also uses appraiserres.dll and initially fails saying 'this PC doesn't meet the specs'. Windows Update then reports this as a failed update with a 'Retry' button.

Deleting appraiserres.dll from C:\$Windows.~BT\Sources is not sufficient to get the update to complete, Windows Update reports 'something went wrong' if appraiserres.dll is missing. I have to replace it with a dummy file named appraiserres.dll then click Retry before Windows Update will complete the upgrade properly.

Hi @Bree

Are you still using the Dev channel? I downloaded the ISO file for the Dev channel from the official page, this ISO file I used with Rufus to create the installation media on a USB stick. In Rufus I just check the box to remove TPM requirement and secure boot.

When Rufus finished creating the installation media, I was able to install Windows 11 Dev from the BIOS. After logging in, I run winver command and it shows me that the build number is 23440.1000

Then I check for updates and when Windows Update is downloading the update you see in the picture (which will increase my build number to 23451.1000) this dialog box appears saying my PC does not meet the requirements. After this I tried Aveyo's famous script which seemed to work, but it was not like that. With the script the update got to 100% and installed without problem, but after restarting my PC and logging in I find that it still has the same build number 23440.1000

Before trying the method of replacing the appraiserres file with a dummy file, have you tried replacing that file with the same file from the Windows 10 ISO?