Cute FTP ver 9 case 00097708

These are Microsoft DLLs, as you might guess.

And I believe Microsoft may have got a patent for what is in those DLLs.

At one time, there was a thing called "DLL Hell".

The file api-ms-win-crt-runtime-l1-1-0.dll is a "mapping" DLL.

It maps something CuteFTP needs, to something a particular OS and DLL contain. You will notice, from the files with that naming convention, that the files are tiny.

api-* do not contain code, they contain linkages, and the file extension of DLL is just a sham.

Just as the EXE on a Metro app is a sham and it's just a manifest.

That's my understanding of the "theory" of these things.

But I'm not really sure these are OS materials. I tried to find copies of some of these before - I found one already on the machine. A second one "wasn't available... anywhere" :-/

So if these are static resources dumped by some Cumulative OS Update, it's not apparent they're all getting dumped, or something.

As far as I'm concerned, this has traded one "DLL Hell" for a second "DLL Hell", and is not an advancement of the arts.

There was some installer for a program I unpacked once, where it had several sets of those kinds of files. And I figured "well, that means these groups support individual OSes". Yet, on other programs, there's only the one set. Like Firefox has a single set of those. You could then run the Firefox EXE through Virustotal and see what DLLs it actually calls. Hopefully not the mapped ones, but the layer underneath.

I'm guessing there are a limitless number of them. If this was a static resource, you'd think Microsoft would just put the whole shitload in a single ZIP and give it to us.

And what should happen, is you'll ask us for api-ms-win-crt-runtime-l1-1-0.dll and we'll find it. Then, 5 seconds later, the program will ask for a second one you don't got. You'll place another post on USENET. Rinse and repeat. Until we hit a brick wall, and one of the ones you need, we dond gots. I've been to this horror show already.

I'm getting hits on Win7, Win8, Win10 for that file. Firefox, Thunderbird, Seamonkey plus some other places.

On Win10, the file is in here:

C:\Windows\System32\downlevel

The folder contains 112 files, including your requested file.

(

Imported DLL: feature1.dll

Windows PC -> feature1.dll HoloLens -> feature1.dll forwarder -> api-feature1-l1-1-0.dll -> feature1_holo.dll IoT -> feature1.dll forwarder -> api-feature1-l1-1-0.dll -> feature1_iot.dll

Direct forwarding:

Imported API set: api-feature1-l1-1-0.dll [see files like this in Firefox folder]

Windows PC -> feature1.dll HoloLens -> feature1_holo.dll IoT -> feature1_iot.dll

Dependencies.exe <===

has been released on GitHub. It does not yet offer the full range of Dependency Walker features, but has been updated to handle Windows API-sets <=== and WinSxS (side-by-side assemblies). "

What that may help with, is make a "list" of the missing goods, so you won't be asking for one at a time. It does not guarantee they are on the machine or anything.

Like maybe

Dependencies.exe cuteftp.exe # try scanning the main executable

There should be a coloring scheme that tells you s*it is missing.

Next, note on Github

Paul

Anyway a long answer with lots of options for you is here:

Install this update package.

OK, I started with a clean Win7 SP1, then added something from here.

---------------------------------------------- <=== On Windows 10, there would be a Downlevel folder with older api-ms for the previous OSes.

Some of the System32 api-ms files have the Hidden attribute set. And, some do not. This means dir /a is needed to list all of them.

That's the progress I've made so far.

I noticed a Microsoft VM I downloaded, had a shitload of them, yet the Programs and Features control panel had *no trace* of how they got into the OS. I wasted a lot of time trying to make a pre-baked VM cough up some secrets. I had to install a VM from the DVD and do it that way, and "guess" at what the source might be.

The files are divided into two sets. And this is just a personal impression, as I can't find the documentation I want.

Some of the entries seem to be related to .NET . The CRT ones are related to VCRedist and Visual Studio. That means, if you have some additional missing ones, that don't have CRT in the name, then as you're posting back with your missing item list, consider tracking down a recent .NET like a 4.7 or a 4.8, and see if installing that helps.

If I just push the button and get wsusoffline to patch up my test OS, it'll pour too much crap into it, and I'll never be able to figure out where the additional files are coming from. My plan is not to ask you to "just patch up your OS", because that's a big ask and could easily break multiple times before you are done.

Paul

• That site is a barrier: "Enter your domain to view your site's login page"

First i download that Windows 10 Universal C Runtime file, gives me WindowsUCRT.zip.

That gives me a chart: The package consists of the following redistributable packages: Target Operating System MSU file X64-based Windows 8.1 requires S14 update(KB2919355), Windows Server 2012 R2: Windows8.1-KB2999226-x64.msu X86-based Windows 8.1 requires S14 update(KB2919355): Windows8.1-KB2999226-x86.msu Arm-based Windows 8.1 requires S14 update(KB2919355): Windows8.1-KB2999226-arm.msu X64-based Windows 8, Windows Server 2012: Windows8-RT-KB2999226-x64.msu X86-based Windows 8: Windows8-RT-KB2999226-x86.msu Arm-based Windows 8: Windows8-RT-KB2999226-arm.msu x64-based Windows 7 SP1 or greater, Windows Server 2008 R2: Windows6.1-KB2999226-x64.msu X86-based Windows 7 SP1 or greater: Windows6.1-KB2999226-x86.msu X64-based Windows Vista SP2 or greater, Windows Server 2008: Windows6.0-KB2999226-x64.msu X86-based Windows Vista SP2 or greater, Windows Server 2008: Windows6.0-KB2999226-x86.msu

Seeing that, i extract Windows6.1-KB2999226-x86.msu and run it.

Tilt: "The update is not applicable to your computer".

Thanks for the try.

Are you sure you're using a 32-bit version of Windows? Because you've downloaded the update package for that Windows version. x86 is 32-bit. x64 is 64-bit.

Sorry, I didn't test that far. If you are running win7 32 bit sp1, send me an email at my from: address minus the obvious tweaks.

The table has only two entries for Win7, one 64 bit and one for 32 bit which is "X86-based Windows 7 SP1 or greater: Windows6.1-KB2999226-x86.msu". And i dern well know i am running 32 bit because i installed to move up from XP numerous years ago and have had to deal with crashes of many kinds.

Thanks.

Only 2 Win7 entries; the 32 bit one is "X86-based Windows 7 SP1 or greater: Windows6.1-KB2999226-x86.msu" and my system is 32 bit.

Carl suggested i put the dll in the C:\Windows\System32 folder. So i moved it from the root; no help, same error message.

Thanks

FYI, Firefox v91 for example, includes (some of) the API set DLLs in its program directory. So, might want to try copying it into Cute FTP's program directory too.

Well, i finally decided to try to install Windows 10 in partition 3 and 4 of the hard drive that had Windows 7 in partition 1 and 2.

Turned out there were absolutely zero options and no control, it got installed where and how it wanted.

Now when i boot, i get Win10 with a desktop, all of my original programs and operation that i had in Win7 with a few very rare exceptions - one being the floppy drive does not exist anywhere in any form.

But get this - CuteFTP version 9 now works! That seems to support my idea that the "absent" dll was compiled into the program.

Why in the hell didn't Globalscape SAY it was a Win10 program in the first place, including in the advertising?

Thanks

Two signing blocks ?