I couldn't find a solution or a way to get to what's going on in the process of the Web Setup on dev environment (Windows). However on test environment CentOS, the following commands worked:
php update/cron.php
php bin/magento setup:cron:run
php bin/magento cron:run
Workaround (if it doesn't work) :
Use composer.
- remove flag file /var/.maintenance.flag
- php bin/magento setup:maintenance:enable
- php bin/magento setup:cache:disable
- [Optional] disable custom modules
- php bin/magento module:status (check status)
- php bin/magento module:disable TheVendor_TheModule
- Edit composer.json
- Change "version": "2.2.4" to "version": "2.2.5"
- Change "magento/product-community-edition": "2.2.4" to "magento/product-community-edition": "2.2.5",
- Prepare Username and Password for repo.magento.com (Magento Public Key and Private Key)
- execute command : "composer update"
- After completion check magento version : php bin/magento --version
- [Optional] rm -rf var/di var/generation (cleanup)
- php bin/magento cache:status (enable if disabled)
- php bin/magento maintenance:status (disable if enabled)
- php bin/magento cache:clean
- php bin/magento cache:flush
- php bin/magento setup:upgrade
- [Optional] disable Static Files Versioning
- php bin/magento setup:di:compile
- php bin/magento setup:static-content:deploy -f
- php bin/magento indexer:reindex
- php bin/magento cache:flush
- php bin/magento cache:clean
- [Optional] chown -R :apache .
- Enable custom modules
- php bin/magento module:enable TheVendor_TheModule
- Conduct Tests
- Say thank you and enjoy :-)
Hope it helps someone!
Note to self: always take a side note of the process, during the process. It's life saver!
