Win Update KB5086672 Windows 11 Out-of-band Update build 26100.8117 (24H2) and 26200.8117 (25H2) - March 31

hader · Apr 5, 2026

gunrunnerjohn said:
I tried CARDFILE.EXE and it just says it can't run on my PC. I think it's a 16 bit application. You may need to run it in a virtual machine.

Looked at this quick. What user Gunrunnerjohn was saying is right. It was original an ancient 16-bit application but now there is also a 32-bit version of this program that will run onto x64-bit systems. (Can run 32 and 64 bit programs. That distinction can be seen in Windows directly. Program Files stores 64-bit programs and 32-bit programs are stored into Program File (x86) )

It seems that this 32-bit program is working (according to the comment below it) on Windows 10/11 x64 systems. It can be found here: Download Cardfile (32-bit) 3.51.1016.1 by Microsoft Corporation | VETUSWARE.COM - the biggest free abandonware collection in the universe So try it.....

Bree · Apr 5, 2026

hader said:
I would recommend to fix your system first with Dism /Online /Cleanup-Image /RestoreHealth and SFC /scannow first and than retry KB5086672 or 26200.8117. Can't see what this OOB has something to do with that access denied issue. The other explanation is that your system was damaged before applying KB5086672. There is a possibility that after applying KB5086672 those DISM and SFC commands were executed and failed to notice this issue. An issue that would require an In-Place-Installment to resolve this situation in the end. An one-off incident because other systems you have did not showed this issue. (I presume. I don't use this hibernation feature in order to a) save space on my C-drive and b) I never had used this feature in the past. I always shutdown my machine....)

I'm away from home at the moment, and only have this system with me. I will not be able to check my other systems until I return on Tuesday.

After trying SFC /ScanNow and DISM commands, and turning hibernation off and back on again (another recommended fix) hibernation was still broken.

I then downloaded the Win11_25H2_EnglishInternational_x64_v2.iso from Microsoft and performed an in-place upgrade. This took me back to 26200.8037. Tested hibernation and it worked normally.

Checked for updates and installed KB5086672. Tested hibernation and it failed.

Unistalled KB5086672. Tested hibernation and it was working again.

Bree · Apr 5, 2026

gunrunnerjohn said:
I tried CARDFILE.EXE and it just says it can't run on my PC. I think it's a 16 bit application. You may need to run it in a virtual machine.

Almost every version of Cardfile.exe was 16-bit. There was just the one 32-bit Cardfile release, that was last issued as part of Windows NT 3.51.

Bree · Apr 5, 2026

hader said:
It seems that this 32-bit program is working (according to the comment below it) on Windows 10/11 x64 systems.

I have been using Cardfile as my address book for years, since Windows 3.1, saving and copying the 16-bit .exe and the .crd data file to each new machine. With Windows 7 I got my first 64-bit OS and had to get the 32-bit version, fortunately I used to have an MSDN subscription and still have the install CD for Windows NT 3.51.

Cardfile has been working fine in Windows 10 and Windows 11 - until now, that is.....

Here it is, still working, in 26200.8037.

Wijnand · Apr 5, 2026

gunrunnerjohn said:
I tried CARDFILE.EXE and it just says it can't run on my PC. I think it's a 16 bit application. You may need to run it in a virtual machine.

I have a 32bit version. It has always worked fine, until this update. The error message is:

It says which says "Cannot find access point of procedure _acmdln_dll in DLL file C:\bin\Cardfile.exe".

hader · Apr 5, 2026

Bree said:
I'm away from home at the moment, and only have this system with me. I will not be able to check my other systems until I return on Tuesday.

After trying SFC /ScanNow and DISM commands, and turning hibernation off and back on again (another recommended fix) hibernation was still broken.

I then downloaded the Win11_25H2_EnglishInternational_x64_v2.iso from Microsoft and performed an in-place upgrade. This took me back to 26200.8037. Tested hibernation and it worked normally.

Checked for updates and installed KB5086672. Tested hibernation and it failed.

Unistalled KB5086672. Tested hibernation and it was working again.

Yes, you also noticed that MS has now placed Version 2 of Windows 11 as the default option on their Windows 11 download page. I had some enormous issues (could not get rid of 380Mb of old update files) with this version which I have not seen before; It kept on complaining that the version of bootloader was not the correct one. In 2 cases even. Saw V1 and wanted V3 (by booting from an Ventoy disk and use this V2 version) and saw V3 and wanted V7 (setup.exe at running Windows). (Those SVN numbers that showed up with Github's: Check-UEFISecureBootVariables-main package) Ran setup.exe of this version 2 as an In-Place-Installment procedure and failed. (Had also an access denied issue (Failed at SAFE_OS during the MIGRATING proces) during moving files to the Windows.old procedure. It could not move them.... Some proces were holding those files locked. Same behavior!!!!.....) The only way I got it working again was to use settings - system - recovery - Reset this PC option. A lengthy proces with I mentioned earlier in this thread. I was not a happy puppy with this. I always used the V1 version of 25H2 in the past with no problems at all. In this case I was fed up after these 2 attempts that I just used the Reset this PC option.

There is a possibility that this V2 version also could not fix your issue as well. I find this situation rather very strange indeed. What more can we do to restore this functionality then?........

I don't know I you have it still somewhere; Use the initial release (I call it now V1) of 25H2 or 26200.6584 to use it as an In-Place-Installment using the regular setup.exe install. If this fails also than I would blame it on the current version of Windows. A very concerning thing. Reset this PC procedure is using the current state to wipe the Component Store clean and download the V2 version as a substitute. Not fixing this issue so to speak.... Whoops!

The other option is to stay on 26200.8037 or 8039 and turn off updates. It is possible that 26200.8116 has an other unknown bug inside it that even 26200.8117 could not fix. (or 26200.8117 even maybe introduced an new bug...) Since this an OOB fix you have to wait on the next real update to see if this issue is by then resolved. I searched. As off now there is no known issue with 26200.8117 and this hibernation file. But never say never. MS and 25H2 are well know to introduce bugs on a regulair basis....

What I encountered and what you encountered can be the same side of the coin. Access denied! There is something wrong inside 8116 and or 8117....

rawintellect · Apr 5, 2026

All of these support .crd files and run on Windows 11 64bit.

Bree · Apr 5, 2026

Wijnand said:
I have a 32bit version. It has always worked fine, until this update. The error message says ... "Cannot find access point of procedure _acmdln_dll in DLL file C:\bin\Cardfile.exe".

Welcome to Eleven Forum.

Your only option for now would be to uninstall this Preview update KB5086672 and hope that April's Patch Tuesday update doesn't have the same issue. As you can see in my post #124 Cardfile runs properly in the March 10th update 26200.8037.

The error message in an English edition is:
"The procedure entry point_acmdin_dll could not be locatedin the dynamic link library C:Temp\CardFile\cardfile.exe"

Wijnand · Apr 5, 2026

Bree said:
Welcome to Eleven Forum.

Your only option for now would be to uninstall this Preview update KB5086672 and hope that April's Patch Tuesday update doesn't have the same issue. As you can see in my post #124 Cardfile runs properly in the March 10th update 26200.8037.

The error message in an English edition is:
"The procedure entry point_acmdin_dll could not be locatedin the dynamic link library C:Temp\CardFile\cardfile.exe"

Thanks, Bree, I'll wait...

hader · Apr 5, 2026

Wijnand said:
I have a 32bit version. It has always worked fine, until this update. The error message is:

It says which says "Cannot find access point of procedure _acmdln_dll in DLL file C:\bin\Cardfile.exe".

It looks to me that Cardfile.exe is calling the ACMDLN.DLL file and Windows could not find it. A registration fault. Deinstall cardfile, clean your registry and install cardfile again. If it still persists;

Can be because of two reasons.

Reinstall/Repair VC++ Redistributables: This is the most common fix. Download and install both the x86 and x64 versions of the latest Microsoft Visual C++ Redistributables from the official Microsoft website. (deinstall and reinstall cardfile again)
Run Dism /Online /Cleanup-Image /RestoreHealth and SFC /scannow to rule out if there is an issue with Windows.

I would suggest to look for an modern alternative. It is possible to read .crd files and extract the information to on a later basis to import them into a modern alternative. In the end it's likely that this version will not work anymore in the future. Progress....

This issue is not very uncommon. There are some issues with other products also. You can look at these suggestions concerning .dll issues also; How to Fix Entry Point Not Found Error?.

Can't see why it earlier it worked and after the update it failed. It's also possible that as Bree suggested to uninstall KB5086672. Then with KB5086672 there are more issues then this one; An issue is there also with the hibernation functionality. (access denied) The troubles with KB5086672 are stacking up. 3 in total..... (Had also a different access denied issue on an other moment also.) And the good news is that that CA2023 has still to arrive also without any issues. As it's looking now? Hold onto your hats everybody....

......

Bree · Apr 5, 2026

hader said:
It looks to me that Cardfile.exe is calling the ACMDLN.DLL file and Windows could not find it. A registration fault. Deinstall cardfile, clean your registry and install cardfile again.

There is no 'install' or 'uninstall' for Cardfile. It is just the single file CARDFILE.EXE that you just copy to a folder and run it from there.

_acmdln is an Internal C runtime global variable.

Microsoft said:
The C runtime (CRT) library contains functions and global variables that are used only to support the public library interface. Some of them are exposed in public headers as implementation details. Although these functions and global variables are accessible through public exports, they're not intended for use by your code. We recommend that you change any code that uses these functions and variables to use public library equivalents instead. These functions may change from version to version. They're listed here to help you identify them. Links are provided when other documentation exists, but in general, these implementation details aren't documented.

Internal CRT globals and value macros
These global variables and macro definitions are used to implement the CRT.

Name
__badioinfo
_acmdln
_commode
_crtAssertBusy
_crtBreakAlloc
__initenv
__lconv
__mb_cur_max
__pioinfo
__unguarded_readlc_active
_wcmdln
__winitenv

cpp-docs/docs/c-runtime-library/internal-crt-globals-and-functions.md at main · MicrosoftDocs/cpp-docs

C++ Documentation. Contribute to MicrosoftDocs/cpp-docs development by creating an account on GitHub.

github.com

These CRT internal variables store the complete command line. They're exposed in the exported symbols for the CRT, but aren't intended for use in your code. _acmdln stores the data as a character string. _wcmdln stores the data as a wide character string. _tcmdln can be defined as either _acmdln or _wcmdln, depending on which is appropriate.

cpp-docs/docs/c-runtime-library/acmdln-tcmdln-wcmdln.md at main · MicrosoftDocs/cpp-docs

C++ Documentation. Contribute to MicrosoftDocs/cpp-docs development by creating an account on GitHub.

github.com

Slavic · Apr 5, 2026

OK, I decided to add my two pence to this research. Because I don't have any distribution of Windows before 98, I downloaded NTWKS351.iso from Internet Archive (archive.org). It took much time... but finally I extracted the required files: cardfile.cnt, cardfile.exe, cardfile.hlp. As expected, it doesn't work in 26200.8117 showing the well known error message. OK, then I extracted the C runtime from this ISO: crtdll.dll to the same place as exe file. And it worked!

I also managed to open the help file (I have the old-style winhlp32.exe) and even modified the executable cardfile.exe for high DPI, which removes blur from menu and other UI elements (such modification by mt.exe usually removes the digital signature, but this file doesn't have it anyway). The result is below.

You may wonder, what is the difference between crtdll.dll in WinNT 3.51 and Windows 11 26200.8117. Size of the first file is 158,952 bytes, while the second has only 60,928 bytes (in SysWOW64). Another interesting fact will be uncovered when you compare their details in Properties. I think it's a result of the last improvements and cleaning up the system DLLs.

TraderGary · Apr 5, 2026

From Wikipedia:

Cardfile.exe debuted with the very first release of Microsoft Windows in 1985, but it is no longer supported in modern Windows versions. You can still run the old executable on current Windows builds, but only as an unsupported legacy program—and recent Windows 11 updates have begun breaking compatibility.

Bree · Apr 5, 2026

Slavic said:
As expected, it doesn't work in 26200.8117 showing the well known error message. OK, then I extracted the C runtime from this ISO: crtdll.dll to the same place as exe file. And it worked!

That is great news. Thanks.

Slavic said:
I think it's a result of the last improvements and cleaning up the system DLLs.

I think you are right. I've tested cardfile in the insider builds Beta, Dev, and Canary. It fails with the same error in all of them.

Bree · Apr 5, 2026

Slavic said:
You may wonder, what is the difference between crtdll.dll in WinNT 3.51 and Windows 11 26200.8117.

That was a wonderful piece of detective work. But you don't have to go back as far as NT3.51 for a compatible crtdll.dll. I have just copied the one from a 26200.8037 install into my Cardfile folder and Cardfile now works in every build up to Canary 29560.1000.

If you still have a install of 26200.8037 you can find it in "C:\Windows\SysWOW64\crtdll.dll"
If you don't have a 26200.8037 machine, but you do have an ISO you can also extract it from the install.esd or install.wim in the sources folder using 7-Zip File Manager.

Wijnand · Apr 6, 2026

Thank you, Bree and Slavic, my cardfile.exe runs again.
I think it's a weird idea of Microsoft to clean up system files that are supposed to provide backward compatibility in a way that makes them less compatible.

We'll see where it takes us...

Bree · Apr 6, 2026

Wijnand said:
I think it's a weird idea of Microsoft to clean up system files that are supposed to provide backward compatibility in a way that makes them less compatible.

It's actually poor coding on Cardfile's part. Seems that it uses unsupported direct access of the internal _acmdln global variable.

Microsoft said:
Although these functions and global variables are accessible through public exports, they're not intended for use by your code. We recommend that you change any code that uses these functions and variables to use public library equivalents instead.

cpp-docs/docs/c-runtime-library/internal-crt-globals-and-functions.md at main · MicrosoftDocs/cpp-docs

Slavic · Apr 6, 2026

Bree said:
It's actually poor coding on Cardfile's part. Seems that it uses unsupported direct access of the internal _acmdln global variable.

Exactly. Cardfile itself is a typical application which could (and should) be programmed using only the publicly available C and Win32 functions. Adding any internal functions and variables was excessive, either by negligence or some kind of developers' elitism.

Anyway, the whole idea to clean up the system DLLs, in particular C library, effectively removing the long existing duplication of crtdll.dll and msvcrt.dll is very good and healthy; supporting and patching any new found bugs in only one library is much better than in two essentially the same. Now crtdll.dll plays a role only as redirection to msvcrt.dll and it can long live in such state.

However, there is a question why not all components of the old C library have got the redirection. I think that MS devs looked at its functions and variables from the point of their usage in modern Windows code and threw away all completely obsolete. This included the vars used in the ancient cardfile.exe. I will be not too surprised if other incompatibilities with some old programs, including those from Microsoft, will be discovered soon or later. On the one side, we know how to fix such problems, but on the other side it's a clear signal that need to say farewell to some good old software.

Bree · Apr 6, 2026

hader said:
An one-off incident because other systems you have did not showed this issue.

Bree said:
I'm away from home at the moment, and only have this system with me. I will not be able to check my other systems until I return.....

I'm home now. I have five other laptops (all are supported devices) that are on 25H2. Not all were on 26200.8177 yet, so I have just updated them all.

Of the five, three resume from hibernation successfully. Two fail to resume from hibernation with the same errors. The two that fail are both the same model, a Dell Latitude 3190. This is the same model as the first one in all respects except that the first is a 2-in-1 with a touch screen and these two are the non-touch version.

So this error is limited to a few very specific devices. My guess is that there is a conflict with a driver unique to these three laptops.

Shonk · Apr 6, 2026

With this update it has reverted back to the old Nvme driver and stopped using the new Native Nvme Driver btw

edit ok i found a workaround

Native Nvme Windows 11 04/26
vivetool /enable /id:60786016,48433719

AI Component	Version
Image Search	1.2603.377.0
Content Extraction	1.2603.377.0
Semantic Analysis	1.2603.377.0
Settings Model	1.2603.377.0

Available	Next Step
	Open Start > Settings > Windows Update. > Advanced options > Optional updates. In the Optional updates available area, you will find the link to download and install available updates. Check for optional updates
	To install this release from the Microsoft Update Catalog, select the option that matches your device architecture (arm64 or x64), and then follow the instructions.

Win Update KB5086672 Windows 11 Out-of-band Update build 26100.8117 (24H2) and 26200.8117 (25H2) - March 31

March 31, 2026 - KB5086672 (OS Builds 26200.8117 and 26100.8117) Out-of-band​

Improvements​

AI Components​

Windows 11 servicing stack update (KB5079387)- 26100.8112​

Known issues in this update​

How to get this update​

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Member

My Computer

Well-known member

My Computer

Mr. Biscuit

My Computer

Well-known member

My Computers

Member

My Computer

Well-known member

My Computer

Well-known member

Internal CRT globals and value macros​

My Computers

Well-known member

My Computer

Stock Market Wizard

My Computers

Well-known member

My Computers

Well-known member

My Computers

Member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Similar threads

March 31, 2026 - KB5086672 (OS Builds 26200.8117 and 26100.8117) Out-of-band

Improvements

AI Components

Windows 11 servicing stack update (KB5079387)- 26100.8112

Known issues in this update

How to get this update

Internal CRT globals and value macros