Hello,
Windows 10 version 1607 is currently in production on our machines. I'm testing the update to Windows 10 version 1704 and I've noticed that Microsoft is forcing Windows Mail down our throats by pinning it to the taskbar. Thanks, Microsoft!
I was thinking of creating a package similar to tis-disable-cortana to uninstall Windows Mail from the PCs.
How can I make the uninstallation happen only after the PC has been upgraded to version 1704?
Thank you.
Uninstall Windows Mail once the Creators Update is installed
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
I'm trying to use the min_os_version of the package control file to achieve what I described. I think I've found a bug related to this feature.
To see what kind of version number it returns, I looked at the wapt source code and found that it uses setuphelpers.windows_version() and that this method uses platform.win32_ver().
The problem is that it doesn't seem to support Windows 10. On a Windows 10 PC, ` platform.win32_ver()` incorrectly returns a value corresponding to Windows 8:
('8', '6.2.9200', '', 'Multiprocessor Free').
Apparently, platform.win32_ver()` uses an API that is no longer supported by Microsoft:
https://stackoverflow.com/questions/325 ... windows-10
EDIT: This is supposed to be fixed in Python >= 2.7.11, but even though `waptpython.exe --version` returns Python 2.7.13 , it doesn't work.
https://stackoverflow.com/questions/334 ... windows-10
To see what kind of version number it returns, I looked at the wapt source code and found that it uses setuphelpers.windows_version() and that this method uses platform.win32_ver().
The problem is that it doesn't seem to support Windows 10. On a Windows 10 PC, ` platform.win32_ver()` incorrectly returns a value corresponding to Windows 8:
('8', '6.2.9200', '', 'Multiprocessor Free').
Apparently, platform.win32_ver()` uses an API that is no longer supported by Microsoft:
https://stackoverflow.com/questions/325 ... windows-10
EDIT: This is supposed to be fixed in Python >= 2.7.11, but even though `waptpython.exe --version` returns Python 2.7.13 , it doesn't work.
https://stackoverflow.com/questions/334 ... windows-10
- dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello f4242,
it's best to start a new thread for a new topic. But anyway, since I took a look at how it works on my machine... In wapt-1.3.13 and wapt-1.5 (which should be released in a few weeks), it works correctly. Which version are you using?
C:\Users\dcardon>waptpython
Python 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import platform
>>> platform.win32_ver()
('10', '10.0.15063', '', u'Multiprocessor Free')
>>>
it's best to start a new thread for a new topic. But anyway, since I took a look at how it works on my machine... In wapt-1.3.13 and wapt-1.5 (which should be released in a few weeks), it works correctly. Which version are you using?
C:\Users\dcardon>waptpython
Python 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import platform
>>> platform.win32_ver()
('10', '10.0.15063', '', u'Multiprocessor Free')
>>>
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Hi,
Here's my version:
C:\wapt>wapt-get --version
Wrapper Win32.exe : wapt-get 1.3.13.0
wapt-get.py 1.3.13.0 common.py 1.3.13.0 setuphelpers.py 1.3.13.0
Hmm, I did the same thing as you with the interactive waptpython and it does indeed work. The erroneous result I got was with pyscripter.
Here's my version:
C:\wapt>wapt-get --version
Wrapper Win32.exe : wapt-get 1.3.13.0
wapt-get.py 1.3.13.0 common.py 1.3.13.0 setuphelpers.py 1.3.13.0
Hmm, I did the same thing as you with the interactive waptpython and it does indeed work. The erroneous result I got was with pyscripter.
Okay, I found it. I needed to import the new version of tis-python27. setuphelpers.windows_version() now returns 10.0.14393 on a Windows 10 PC (Anniversary Update) when launched from pyscripter.
But I still have a problem
I add this line to my file control:
I build my package... and poof, the line disappears! My package then installs regardless of the Windows version used. Any idea what's wrong?
But I still have a problem
I add this line to my file control:
Code: Select all
min_os_version : 10.0.15063- dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
PyScripter runs with the locally installed Python in c:\python27 (the default installation directory). So yes, it needs to be kept up to date.
The min_os_version attribute is not supported in WAPT 1.3. You have to wait for version 1.5.
The min_os_version attribute is not supported in WAPT 1.3. You have to wait for version 1.5.
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Okay. The documentation needs to be corrected; it states that this has been available since version 1.3.9: https://www.wapt.fr/fr/doc/CreationPaqu ... index.html.
Thank you!
Thank you!
While waiting for version 1.5, I thought about adding a condition to my installation script to verify that Windows is indeed version 1703 before proceeding. I know how to check the current Windows version, but I was wondering how to make the package attempt to reinstall itself until Windows is updated?
I imagine I need to force the package to fail? How?
Thanks!
I imagine I need to force the package to fail? How?
Thanks!
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
