Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Anaconda navigator not working

283 views
Skip to first unread message

Liya Ann Sunny

unread,
Jun 20, 2021, 12:21:14 AM6/20/21
to
After installing Anaconda, I tried to open the anaconda navigator but it did not work.
When i check in anaconda prompt by running code
>>>anaconda
it got error like this
(base) C:\Users\Acer>anaconda
Traceback (most recent call last):
File "C:\Users\Acer\anaconda3\Scripts\anaconda-script.py", line 6, in <module>
from binstar_client.scripts.cli import main
File "C:\Users\Acer\anaconda3\lib\site-packages\binstar_client\__init__.py", line 17, in <module>
from .utils import compute_hash, jencode, pv
File "C:\Users\Acer\anaconda3\lib\site-packages\binstar_client\utils\__init__.py", line 17, in <module>
from .config import (get_server_api, dirs, load_token, store_token,
File "C:\Users\Acer\anaconda3\lib\site-packages\binstar_client\utils\config.py", line 54, in <module>
USER_LOGDIR = dirs.user_log_dir
File "C:\Users\Acer\anaconda3\lib\site-packages\binstar_client\utils\appdirs.py", line 257, in user_log_dir
return user_log_dir(self.appname, self.appauthor,
File "C:\Users\Acer\anaconda3\lib\site-packages\binstar_client\utils\appdirs.py", line 205, in user_log_dir
path = user_data_dir(appname, appauthor, version); version = False
File "C:\Users\Acer\anaconda3\lib\site-packages\binstar_client\utils\appdirs.py", line 67, in user_data_dir
path = os.path.join(_get_win_folder(const), appauthor, appname)
File "C:\Users\Acer\anaconda3\lib\site-packages\binstar_client\utils\appdirs.py", line 284, in _get_win_folder_with_pywin32
from win32com.shell import shellcon, shell
ImportError: DLL load failed while importing shell: %1 is not a valid Win32 application.

what is its solution?

Rob Cliffe

unread,
Jun 20, 2021, 9:08:31 PM6/20/21
to
I'm afraid I can't help at all, but I have many times (well, it feels
like many) encountered the
    "%1 is not a valid Win32 application"
error message.  It looks like a format string that has not been given an
argument to format.
I would guess it's a bug either in Windows or somewhere in Python.
Can anybody shed light on this?
Best wishes
Rob Cliffe
PS I have a very vague idea it's to do with mixing 32-bit and 64-bit
software.
0 new messages