MySQL instance lost when upgrading to Windows 10
5,199
Solution 1
You can manually put the service back as follows:
STEP 01) Open the Windows CLI as Administrator
STEP 02) cd C:\Program Files (x86)\MySQL\MySQL 5.6\bin
or wherever mysqld.exe
resides
STEP 03) Reinstall the service
mysqld --install
That's it.
I have mentioned this before in ServerFault and DBA StackExchange
GIVE IT A TRY !!!
Solution 2
All you need to do is reconfigure your current server. A nice step by step tutorial including screenshots can be found here, you do like this:
- First, open the application MySQL Installer – Community and click on Reconfigure
- Setup TCP/IP Port Number and Firewall
- Check Configure MySQL Server as a Windows Service and also check Start the MySQL Server at System Startup
- Apply the server configuration and your done!
Related videos on Youtube
Author by
Jago
Updated on September 18, 2022Comments
-
Jago almost 2 years
I had a running instance of MySQL 5.6 in my Windows 8.1. After upgrading to Windows 10, such instance is gone, including the Windows service for it.
Server data files are however intact. What would be the best way to recover or re-create the exact same instance (or the most similar) back in Windows 10?
-
RolandoMySQLDBA almost 9 yearsShame on you for putting
windows-10-upgrade
tag in this question. Those two phrases put together have no place in the Universe. ;-) ( It's more like window-10-damage-control )
-
-
fixer1234 almost 8 yearsWelcome to Super User. External links can break or be unavailable, in which case your answer would not be useful. Please include the essential information within your answer and use the link for attribution and further reading. Thanks.
-
mikato almost 8 yearsI used this method to fix the same problem that Jago had, but it was not able to execute the last step of the Reconfigure... it couldn't start the service. I found it was loading a fresh default my.ini each time I ran it. I had a different MySQL data directory though (datadir in my.ini). Even if I adjusted the datadir in the my.ini as the reconfigure was running it wouldn't take. But I found all I had to do was cancel the MySQL reconfigure, make sure the datadir was correct in my.ini, go into Windows Services and start the new MySQL service there. That worked. What a headache though.