WindowsError: [Error 0] The operation completed successfully for exe() after upgrading to 5.5.0
See original GitHub issueTested with Python 2.7.13 and 3.7.1, Windows 10 1809 (10.0.17763.0). psutil version: 5.5.0
It fails on ‘Secure System’ process, only when Python was run as an Administrator:
Python 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:53:40) [MSC v.1500 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import psutil
>>> [p for p in psutil.process_iter()]
[psutil.Process(pid=0, name='System Idle Process', started='2018-11-06 04:18:12'), psutil.Process(pid=4, name='System', started='2018-11-06 04:18:12'), Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "C:\Python27\lib\site-packages\psutil\__init__.py", line 395, in __str__
info["name"] = self.name()
File "C:\Python27\lib\site-packages\psutil\__init__.py", line 609, in name
name = self._proc.name()
File "C:\Python27\lib\site-packages\psutil\_pswindows.py", line 635, in wrapper
return fun(self, *args, **kwargs)
File "C:\Python27\lib\site-packages\psutil\_pswindows.py", line 687, in name
return py2_strencode(os.path.basename(self.exe()))
File "C:\Python27\lib\site-packages\psutil\_pswindows.py", line 635, in wrapper
return fun(self, *args, **kwargs)
File "C:\Python27\lib\site-packages\psutil\_pswindows.py", line 701, in exe
return py2_strencode(convert_dos_path(cext.proc_exe(self.pid)))
WindowsError: [Error 0] The operation completed successfully
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:14 (8 by maintainers)
Top Results From Across the Web
Fix Windows Error 0 ERROR_SUCCESS - TechCult
How to Fix Windows Error 0 ERROR_SUCCESS the operation completed successfully: Change Account Type, Disable Proxy, Modify LAN Settings.
Read more >How to fix the Windows System Error 0 ERROR_SUCCESS
This article features error number Code 0, commonly known as ERROR_SUCCESS and it is described as The operation completed successfully.
Read more >Upgrade error codes - Windows Client - Microsoft Learn
If the upgrade process isn't successful, Windows Setup will return two codes: A result code: The result code corresponds to a specific Win32 ......
Read more >This npm install is not working on Windows - node.js
After countless hours of debugging and researching, I decided to install on a different machine to see if the problem was with my...
Read more >VMware Horizon Client Install Error on Windows 10 x64
Hello, I have a problem installing VMware horizon client 5.3 and 4.10 in my ThinkPC after i formatted my computer which has the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Avoiding to convert the DOS/win32 path format would be a clear win. Before proceeding though I would investigate how both APIs behave and if there are differences in terms of returned paths and (above all) permissions. QueryFullProcessImageNameW may work better but we should first make sure it won’t result in more AccessDenied exceptions.
OK, I also included Win XP support (not tested though). Closing this out as fixed. Thank you guys for the support.