Saved Bookmarks
| 1. |
Solve : Cannot Accept Control messages At This Time? |
|
Answer» Hello guys (again) It has something to do with a root file being deleted. ShelExecuteEx is a root file. My sister had to reload her computer when it did that. You might want to weight and see if anybody can tell you else wise. If not well... BOOM. I'd back-up first. Thanks HELPHELP , just this second solved it, its the " Application information service" i had to backtrack what i had been doing today, and i had mistakenly set this service to manual, the service had already started, but i had stopped it, and set it to manual, and basically could not do a thing. But a few days ago, i had printed the default settings to the services in windows 7, and had kept a list of what services i changed, and noticed the mistake. To fix this you go into safe mode, and just start the service again, and set it to manual. http://www.blackviper.com/Windows_7/Services/Application_Information.htmGlad to help.I know a little about computers, but more about the mother board than the computer its self. Quote from: HELPHELP on February 22, 2010, 12:52:47 PM ShelExecuteEx is a root file. No, it's a FUNCTION in shell32.dll. The "Application Information Service" is a service added to Windows Vista and 7 to help support Elevation of processes. Basically, it stops a non-elevated program from being the parent process of a elevated program (which may introduce security flaws, in that the parent process can access parts of the elevated process that may violate security). Instead, when a program uses ShellExecuteEx/ShellExecute to run a program, the service is called and performs the execution. So, If the program is to be run elevated then the elevated program will be a child process of the service rather then the possibly untrustable program that called ShellExecute/ShellExecuteEx. Yes, sorry. But it is a root process that is needed for your computer to work properly.Quote from: HELPHELP on February 22, 2010, 05:19:55 PM Yes, sorry. But it is a root process that is needed for your computer to work properly. No. It's not a process. it's a function. in shell32.dll. Shell32.dll could, vaguely speaking, be considered as a "root file" but at the same time you cannot boot without the proper version of shell32.dll to BEGIN with. This particular issue had nothing to do with ShellExecuteEx or Shell32.dll; the very same issue would have occured had an application tried to execute an elevated application using CreateProcess() in kernel32.dll- the problem was SIMPLY that the service was not started. the Service is not a critical service, by any means. and in fact, disabling all UAC options and security of that nature would have also "fixed" the problem, since with the entire UAC infrastructure disabled, the service is not used at all.Ok. you beat me. The important thing is carlrowley1 got his CPU working.Quote from: HELPHELP on February 22, 2010, 05:30:53 PM Ok. you beat me. The important thing is carlrowley1 got his CPU working. But the CPU was never broken. hee hee.Hee hee. It had a problem though.Quote from: HELPHELP on February 22, 2010, 06:31:03 PM Hee hee. It had a problem though. The Central processing Unit? There was nothing wrong with it at all Quote from: BC_Programmer on February 22, 2010, 07:17:41 PM The Central processing Unit? There was nothing wrong with it at all Hey, great discussion there, thanks for the added information about ShellExecuteEX BC_Programmer. I just looked it up myself. ShellExecuteEX (Function) http://msdn.microsoft.com/en-us/library/bb762154(VS.85).aspx Quote from: carlrowley1 on February 22, 2010, 10:45:19 PM
Yeah I was going to post a link, either to that, or ShellExecute... Guess I forget, heh.Thanks for the link. Guess I need to read more stuff to get the names right. |
|