Windows 10: wininet.dll : Access violation read to 0x00490000 in 'wininet.dll'

Dear colleagues. I use a wininet.dll for reading a file from the server and receive an error message: Access violation read to 0x00490000 in 'wininet.dll'. Unfortunately, can't find any information about the reason for this exception and how to solve this issue. I will be thankful for any information.

:)

 

WinInet Broker and Cache servers issue at startup

Since a couple of weeks I've been nagged by the error screens on the Distributed COM errors. After examining Even Viewer it's clear it refers to the WinInet Broker Server and WinInet Cache server instances. The errors are well-known 10010 errors saying: The server {xxxxx} did not register with DCOM within the required timeout.

The problem is that the standard solution recommended on many forums (and which in fact I've already successfully used in the past) doesn't work. The solution involves granting additional permissions in the DCOM Configuration Editor. In my case I've added all recommended permissions and when it failed to have any effect I've added virtually any user/service I could find to have the right to launch those. Yet, I'm still obtaining those errors at the startup... It takes about 7-8 errors related to WinInet Broker and 1-2 related to WinInet Cache.

Unfortunately I can't really identify the moment in time I've started to receive those issues, so I can't really bind them to any specific application I might have installed.

Can anyone suggest any further tips on how to investigate the issues source and how to get rid of it? Since this is a work laptop I can't really reinstall the OS, but I'm having admin rights, so I can modify it.

 

Accessing the DLL and Registry

I'm not sure what you think 'the DLL' is but whatever you have in mind is mistaken. There is no such thing as the DLL.

Actually there are thousands of .DLL files, each with a specific purpose. DLL stand for Dynamic Link Library, each .dll file is a library of executable code providing functions that can be called by other programs and code. There is nothing there for a human to read.

To list all the DLLs that Windows uses, open a command prompt and type the command: dir C:\windows\system32\*.dll

This produces a list of 3242 File(s) for my machine. Now, which one is the DLL you want to look at? For further understanding of what a DLL is (and what it is not) read the Microsoft link Berton gave you in post #2. For a less technical view, read: Lifewire - What Is a DLL File? (Dynamic Link Library)

The Registry is another matter, that is readable (and editable) using Regedit. However, it is rather opaque reading and the fact that any changes you make in Regedit are effective instantly (there's no 'Save' option that you can back out of, you are modifying the system as it runs) it is best not to look unless you know what you are doing.

 

Accessing the DLL and Registry

Depends what you want to do with a dll access its code so you can call it? This site has tools for dll DLL Export Viewer - view exported functions list in Windows DLL.

You can view icons in dlls https://www.winhelponline.com/blog/i...perties-sheet/