_findvs failing on Windows 10 (Release build only)

[WildCard65]

BPO	32928
Nosy	@pfmoore, @tjguk, @merwok, @zware, @zooba, @dstufft, @WildCard65

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2018-02-24.15:56:40.233>
created_at = <Date 2018-02-23.23:10:15.644>
labels = ['3.8', 'type-crash', 'extension-modules', 'invalid', '3.7', 'library', 'OS-windows']
title = '_findvs failing on Windows 10 (Release build only)'
updated_at = <Date 2018-02-24.16:58:10.586>
user = 'https://github.com/WildCard65'

bugs.python.org fields:

activity = <Date 2018-02-24.16:58:10.586>
actor = 'WildCard65'
assignee = 'none'
closed = True
closed_date = <Date 2018-02-24.15:56:40.233>
closer = 'WildCard65'
components = ['Distutils', 'Extension Modules', 'Library (Lib)', 'Windows']
creation = <Date 2018-02-23.23:10:15.644>
creator = 'WildCard65'
dependencies = []
files = []
hgrepos = []
issue_num = 32928
keywords = []
message_count = 6.0
messages = ['312673', '312678', '312679', '312728', '312731', '312732']
nosy_count = 7.0
nosy_names = ['paul.moore', 'tim.golden', 'eric.araujo', 'zach.ware', 'steve.dower', 'dstufft', 'WildCard65']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'crash'
url = 'https://bugs.python.org/issue32928'
versions = ['Python 3.6', 'Python 3.7', 'Python 3.8']

[WildCard65]

The distutils module _findvs is failing on my Windows 10 PRO machine with the following error: OSError: Error 80070002

Note: Building Python 3.6 in debug for some reason doesn't cause the error.

[zooba]

You mean build? Or use?

Can you share build logs?

[WildCard65]

Use, when distutils calls findall in the module, it results in the OSError being thrown.

[WildCard65]

Looks like something wierd about my computer as the powershell module that interacts with the API also has the issue with Windows reporting "File not found" for a 2nd instance (maybe Community edition of VS)

[zooba]

If you think it should be working, go ahead and use the Report a Problem tool in VS to let the team know about the PowerShell module. There might be a case that isn't handled properly in their code that they can fix (obviously they don't know/care about the Python module, but we are using the same API).

[WildCard65]

The powershell module that interacts with the API works if I don't supply "-All", supplying said option produces the same issue that is plagues me when _findvs.findall() is used.