If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Win7 procedure entry point not located
My new Win7pro pain-in-the-ass keeps telling me:
"The procedure entry point [something] could not be located and.... appupdater.exe Entry poing not found" what the hell? I'm in a bad mood. Spending the month trying to make a new computer work....... HELP ! |
Ads |
#2
|
|||
|
|||
Win7 procedure entry point not located
masonc wrote:
My new Win7pro pain-in-the-ass keeps telling me: "The procedure entry point [something] could not be located and.... appupdater.exe Entry poing not found" what the hell? I'm in a bad mood. Spending the month trying to make a new computer work....... HELP ! The appupdater thing is pretty generic, and I doubt that by itself is going to lead anywhere productive. Do you have any more exact error messages with unique names in them, that are going to be easier to trace ? I can't tell from what I've seen so far, whether this is a Windows malfunction, or it is evidence of malware. That's part of the identification process, is deciding whether to do a site search against bleepingcomputer.com if it is malware, or against microsoft.com if it is a Windows defect or a Windows technology. I use searches like this. site:bleepingcomputer.com appupdater.exe If we had the name of your procedure entry point, I bet that would be worth something. HTH, Paul |
#3
|
|||
|
|||
Win7 procedure entry point not located
masonc wrote:
My new Win7pro pain-in-the-ass keeps telling me: "The procedure entry point [something] could not be located and.... appupdater.exe Entry poing not found" If appupdater.exe is shown in Task Manager's Processes tab, right-click on it and look at its Properties which will tell you the path to the executable. "procedure entry point" is for a DLL (dynamically linked library). When calling a method (aka function) from a DLL, an entry point (offset) is needed to find the method. Do a file search on appupdater.dll to see if you find one which may indicate for what program it belongs. If the DLL file is missing then the caller (.exe program) can't find the DLL lib from which to call its methods. PC-Doctor (sometimes bundleware included by Dell or Lenovo) is junk. Uninstall it. |
#4
|
|||
|
|||
Win7 procedure entry point not located
On 10/01/2015 09:37 PM, masonc wrote:
My new Win7pro pain-in-the-ass keeps telling me: "The procedure entry point [something] could not be located and.... appupdater.exe Entry poing not found" what the hell? I'm in a bad mood. Spending the month trying to make a new computer work....... HELP ! Could be malware that was removed by your virus or malware checker but it is still being referenced. Run "msconfig" and if it's listed, uncheck it |
#5
|
|||
|
|||
Win7 procedure entry point not located
masonc wrote on 10/01/2015 10:37 PM:
My new Win7pro pain-in-the-ass keeps telling me: "The procedure entry point [something] could not be located and.... appupdater.exe Entry poing not found" what the hell? I'm in a bad mood. Spending the month trying to make a new computer work....... HELP ! What might help is informing the group when you actually see that message. -- ...winston msft mvp windows experience |
#6
|
|||
|
|||
Win7 procedure entry point not located
|
#7
|
|||
|
|||
Win7 procedure entry point not located
On Thu, 01 Oct 2015 19:37:04 -0700, masonc
wrote: My new Win7pro keeps telling me when I attempt Control Panel / System / System Protection quote: The procedure entry point ucrtbase.terminate could not be located in the dynamic link library api-ms-win-crt-runtime-11-1-0.dll unquote Three taps on "OK" makes it disappear. "Also, I've seen: SystemPropertiesProtection.exe Entry Point Not Found" (same .dll) also: " appupdater.exe Entry point not found" {same .dll} and there are 12 (twelve) "notepad.exe" 's in Win7 -- what the hell is that all about? ok, I'm in a bad mood. |
#8
|
|||
|
|||
Win7 procedure entry point not located
Ken1943 wrote:
On Fri, 02 Oct 2015 14:37:45 -0700, masonc wrote: On Thu, 01 Oct 2015 19:37:04 -0700, masonc wrote: My new Win7pro keeps telling me when I attempt Control Panel / System / System Protection quote: The procedure entry point ucrtbase.terminate could not be located in the dynamic link library api-ms-win-crt-runtime-11-1-0.dll unquote Three taps on "OK" makes it disappear. "Also, I've seen: SystemPropertiesProtection.exe Entry Point Not Found" (same .dll) also: " appupdater.exe Entry point not found" {same .dll} and there are 12 (twelve) "notepad.exe" 's in Win7 -- what the hell is that all about? ok, I'm in a bad mood. No expert, but sounds like a file location got lost. I would try chkdsk C: /r to try and fix it. Ken1943 This update, released Aug 22, 2015, has files with names like https://support.microsoft.com/en-us/kb/2999226 Api-ms-win-crt-runtime-l1-1-0.dll 10.0.10240.16390 16,224 18-Jul-2015 13:14 x64 The release info, says those are Windows 10 builds of a Universal App library. And some stackexchange thread, said something about "wishIhadapackagemanager" or somesuch. It's possible the OP has installed an SDK, has Visual Studio on the machine, and the wrong files are getting picked up. There's some relationship to Visual Studio but I can't figure it out from the utter confusion in this thread. This thread sounds like a bunch of IT guys trying to fix a problem from their end, caused by a software developer. https://social.msdn.microsoft.com/Fo...?forum=vssetup That doesn't explain the Notepad though. Unless Notepad is being launched instead of a SVCHOST or something, or the Task Manager is labeling instances of SVCHOST as Notepad. Pretty weird. It's even possible a file extension has the wrong mapping. When someone brought that KB2999226 update to our attention, I thought it was an entirely unique thing. But files with names like that, may already have been distributed over the last number of years, and may have entered the computer via other kinds of installations. So if the problem didn't exist before Aug.22, it's possibly related to that update. But I'm still not finding a "developer class" thread that can explain how those libraries are supposed to work. Paul |
#9
|
|||
|
|||
Win7 procedure entry point not located
masonc wrote:
masonc wrote: My new Win7pro keeps telling me when I attempt Control Panel / System / System Protection That runs C:\Windows\system32\systempropertiesprotection.exe (that you mention later). The procedure entry point ucrtbase.terminate could not be located in the dynamic link library api-ms-win-crt-runtime-11-1-0.dll Tells you that the DLL (api-ms-win-crt-runtime-11-1-0.dll) does not have the method named "ucrtbase.terminate". There is no ucrtbase.dll on my Windows 7 Home x64 setup; however, I reject (do not install and hide in further update checks) the bogus Win7 "updates" from Microsoft: they have nothing to do with Win7 but instead are for telemetry (spying) and for migration to Win10. http://windows10dll.nirsoft.net/ucrtbase_dll.html That indicates ucrtbase.dll is a Win10 file and notes it links to the runtime files similar that you noted in the error message. The "ucrt" looks like the "universal c runtime" update that Microsoft recently tried to push to Win7/8 hosts: it is a CRT to provide app development on Windows 10 but supposedly to allow Win10 apps to run back on Win7/8. https://support.microsoft.com/en-us/kb/2999226 The api-ms-win-crt-runtime-11-1-0.dll is listed as one of the included files in the UCRT update; however, you wrote "11-1-0" but it is "L1-1-0" (replace your "11" with "L1"). If you do not have any Win10 apps that you are trying to run back on Win7 then you don't need the UCRT lib. See the other thread titled "Windows 7 Optional Update - KB2999226?" in this newsgroup. Three taps on "OK" makes it disappear. "Also, I've seen: SystemPropertiesProtection.exe Entry Point Not Found" (same .dll) also: " appupdater.exe Entry point not found" {same .dll} You need to review Microsoft's update BEFORE retrieving and installing them. Microsoft has been sneaking in telemetry updates to let them spy on your use of Windows 7/8. They have also been sneaking in update that have nothing to do with Windows 7/8 but are for migration to Windows 10. Since you have this Win10 update installed in Win7, you likely allowed without review their other Win10 updates in Win7, like the infamous "Get Win10 app" (KB3035583). and there are 12 (twelve) "notepad.exe" 's in Win7 -- what the hell is that all about? ok, I'm in a bad mood. I have 3 instances under: C:\Windows C:\Windows\System32 (*) C:\Windows\SysWOW64 (***) (*) "fc /b c:\windows\notepad.exe c:\windows\system32\notepad.exe" shows no differences (the files are the same). (**) This is the one loaded if no path is specified. (***) I have 64-bit Windows 7 installed. See: http://www.samlogic.net/articles/32-...6-syswow64.htm Other 9 instances are under the C:\Windows\winsxs. See: http://www.thewindowsclub.com/winsxs-folder-windows-7-8 (found via https://www.bing.com/search?q=window...nsxs%20folder). |
Thread Tools | |
Display Modes | Rate This Thread |
|
|