Windows 10 on macbook 2017 by bootcamp

you get an error because mysqld dies.

you can try :

mkdir C:\datadir
mysqld --datadir=C:\datadir --skip-grant-tables --console

to find out why it does (and attach the output to the bug report)

I have come across a similar report for MySQL, mentioning macOS and bootcamp, https://bugs.mysql.com/bug.php?id=85020 . so maybe it just does not work because it does not support asynchronous IO on whatever reason.

Also, https://stackoverflow.com/questions/47006605/installing-xampp-on-windows-10-via-bootcamp

Thank you so much for fast response, here you go:

C:\Windows\system32>mkdir C:\datadir

C:\Windows\system32>cd C:\Users\Moh'd N. Alfayez\Desktop\mariadb-10.2.16-winx64\bin

C:\Users\Moh'd N. Alfayez\Desktop\mariadb-10.2.16-winx64\bin>mysqld --datadir=C:\datadir --skip-grant-tables --console
2018-06-27 14:49:59 8532 [Note] mysqld (mysqld 10.2.16-MariaDB) starting as process 10280 ...
2018-06-27 14:49:59 8532 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-06-27 14:49:59 8532 [Note] InnoDB: Uses event mutexes
2018-06-27 14:49:59 8532 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-06-27 14:49:59 8532 [Note] InnoDB: Number of pools: 1
2018-06-27 14:49:59 8532 [Note] InnoDB: Using SSE2 crc32 instructions
2018-06-27 14:49:59 8532 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-06-27 14:49:59 8532 [Note] InnoDB: Completed initialization of buffer pool
2018-06-27 14:49:59 8532 [Note] InnoDB: The first innodb_system data file 'ibdata1' did not exist. A new tablespace will be created!
2018-06-27 14:49:59 8532 [Note] InnoDB: Setting file '.\ibdata1' size to 12 MB. Physically writing the file full; Please wait ...
2018-06-27 14:49:59 8532 [Note] InnoDB: File '.\ibdata1' size is now 12 MB.
2018-06-27 14:49:59 8532 [Note] InnoDB: Setting log file .\ib_logfile101 size to 50331648 bytes
2018-06-27 14:49:59 8532 [Note] InnoDB: Setting log file .\ib_logfile1 size to 50331648 bytes
2018-06-27 14:49:59 8532 [Warning] InnoDB: Retry attempts for writing partial data failed.
2018-06-27 14:49:59 8532 [ERROR] InnoDB: Write to file .\ib_logfile101 failed at offset 0, 512 bytes should have been written, only 0 were written. Operating system error number 2. Check that your OS and file system support files of this size. Check also that the disk is not full or a disk quota exceeded.
2018-06-27 14:49:59 8532 [ERROR] InnoDB: Error number 2 means 'No such file or directory'
2018-06-27 14:49:59 8532 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2018-06-27 14:49:59 0x2154 InnoDB: Assertion failure in file d:\winx64-packages\build\src\storage\innobase\fil\fil0fil.cc line 5209
InnoDB: Failing assertion: req_type.is_dblwr_recover() || err == DB_SUCCESS
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/
InnoDB: about forcing recovery.
180627 14:49:59 [ERROR] mysqld got exception 0x80000003 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.2.16-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=65537
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 136062 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
mysqld.exe!my_sigabrt_handler()[my_thr_init.c:487]
mysqld.exe!raise()[signal.cpp:516]
mysqld.exe!abort()[abort.cpp:71]
mysqld.exe!ut_dbg_assertion_failed()[ut0dbg.cc:61]
mysqld.exe!fil_io()[fil0fil.cc:5209]
mysqld.exe!log_group_file_header_flush()[log0log.cc:911]
mysqld.exe!log_group_write_buf()[log0log.cc:975]
mysqld.exe!log_write_up_to()[log0log.cc:1291]
mysqld.exe!log_checkpoint()[log0log.cc:1719]
mysqld.exe!log_make_checkpoint_at()[log0log.cc:1765]
mysqld.exe!recv_reset_logs()[log0recv.cc:3641]
mysqld.exe!create_log_files()[srv0start.cc:510]
mysqld.exe!innobase_start_or_create_for_mysql()[srv0start.cc:1962]
mysqld.exe!innobase_init()[ha_innodb.cc:4393]
mysqld.exe!ha_initialize_handlerton()[handler.cc:520]
mysqld.exe!plugin_initialize()[sql_plugin.cc:1416]
mysqld.exe!plugin_init()[sql_plugin.cc:1697]
mysqld.exe!init_server_components()[mysqld.cc:5285]
mysqld.exe!win_main()[mysqld.cc:5876]
mysqld.exe!mysql_service()[mysqld.cc:6132]
mysqld.exe!mysqld_main()[mysqld.cc:6327]
mysqld.exe!__scrt_common_main_seh()[exe_common.inl:283]
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

seems to be the same as https://bugs.mysql.com/bug.php?id=85020
write fails into the log file. I've no idea why. Unfortunately our log output on Windows is incorrect (does not preserve Windows error from WriteFile) . I fixed it now with https://github.com/MariaDB/server/commit/04677f44c7a0faee366de265c92175daadf45bc9

Strange question maybe, but is C:\ partition NTFS? What is the file system there?

yes its NTFS

Thanks!
I might have an idea.

Can you run below command (as administrator) and attach the output

fsutil fsinfo volumeinfo C: && fsutil fsinfo ntfsinfo C: && fsutil fsinfo sectorinfo C:

Also, are you able to successfully run

mysqld --datadir=C:\datadir --skip-grant-tables --innodb_flush_log_at_trx_commit=2 --console

?
(--innodb_flush_log_at_trx_commit=2 is crucial here)

My idea is that you have a disk with sector size 4K. Usually, those disks also support emulation of traditional 512byte sectors, but maybe it is not in your case.
It is likely, that unbuffered IO with mismatches sector size could fail.

https://stackoverflow.com/questions/15216374/writefile-failure-with-error-code-87-in-4096-bytes-per-sector-disk

here u go:

C:\Windows\system32>fsutil fsinfo volumeinfo C: && fsutil fsinfo ntfsinfo C: && fsutil fsinfo sectorinfo C:
Volume Name : BOOTCAMP
Volume Serial Number : 0x2469ff7
Max Component Length : 255
File System Name : NTFS
Is ReadWrite
Not Thinly-Provisioned
Supports Case-sensitive filenames
Preserves Case of filenames
Supports Unicode in filenames
Preserves & Enforces ACL's
Supports file-based Compression
Supports Disk Quotas
Supports Sparse files
Supports Reparse Points
Returns Handle Close Result Information
Supports POSIX-style Unlink and Rename
Supports Object Identifiers
Supports Encrypted File System
Supports Named Streams
Supports Transactions
Supports Hard Links
Supports Extended Attributes
Supports Open By FileID
Supports USN Journal
NTFS Volume Serial Number : 0x34f5ee1202469ff7
NTFS Version : 3.1
LFS Version : 2.0
Number Sectors : 0x0000000002f05eff
Total Clusters : 0x0000000002f05eff
Free Clusters : 0x00000000023b1619
Total Reserved : 0x0000000000000fab
Bytes Per Sector : 4096
Bytes Per Physical Sector : 4096
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 4096
Clusters Per FileRecord Segment : 1
Mft Valid Data Length : 0x0000000034300000
Mft Start Lcn : 0x0000000000000004
Mft2 Start Lcn : 0x0000000001782f7f
Mft Zone Start : 0x000000000052dc80
Mft Zone End : 0x0000000000538bc0
Max Device Trim Extent Count : 256
Max Device Trim Byte Count : 0xffffffff
Max Volume Trim Extent Count : 62
Max Volume Trim Byte Count : 0x40000000
Resource Manager Identifier : 3F94580A-796C-11E8-A09D-806E6F6E6963
LogicalBytesPerSector : 4096
PhysicalBytesPerSectorForAtomicity : 4096
PhysicalBytesPerSectorForPerformance : 4096
FileSystemEffectivePhysicalBytesPerSectorForAtomicity : 4096
Device Alignment : Aligned (0x000)
Partition alignment on device : Aligned (0x000)
No Seek Penalty
Trim Supported
Not DAX capable
Not Thinly-Provisioned

and for mysqlid faild and here is the response:

C:\Windows\system32>cd C:\Users\Moh'd N. Alfayez\Desktop\mariadb-10.2.16-winx64\bin

C:\Users\Moh'd N. Alfayez\Desktop\mariadb-10.2.16-winx64\bin>mysqld --datadir=C:\datadir --skip-grant-tables --innodb_flush_log_at_trx_commit=2 --console
2018-06-29 23:09:28 9776 [Note] mysqld (mysqld 10.2.16-MariaDB) starting as process 868 ...
2018-06-29 23:09:28 9776 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-06-29 23:09:28 9776 [Note] InnoDB: Uses event mutexes
2018-06-29 23:09:28 9776 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-06-29 23:09:28 9776 [Note] InnoDB: Number of pools: 1
2018-06-29 23:09:28 9776 [Note] InnoDB: Using SSE2 crc32 instructions
2018-06-29 23:09:28 9776 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-06-29 23:09:28 9776 [Note] InnoDB: Completed initialization of buffer pool
2018-06-29 23:09:28 9776 [ERROR] InnoDB: Header page consists of zero bytes in datafile: .\ibdata1, Space ID:0, Flags: 0. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2018-06-29 23:09:28 9776 [ERROR] InnoDB: Corrupted page [page id: space=0, page number=0] of datafile '.\ibdata1' could not be found in the doublewrite buffer.
2018-06-29 23:09:28 9776 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
2018-06-29 23:09:28 9776 [Note] InnoDB: Starting shutdown...
2018-06-29 23:09:28 9776 [ERROR] Plugin 'InnoDB' init function returned error.
2018-06-29 23:09:28 9776 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2018-06-29 23:09:28 9776 [Note] Plugin 'FEEDBACK' is disabled.
2018-06-29 23:09:28 9776 [ERROR] Unknown/unsupported storage engine: InnoDB
2018-06-29 23:09:28 9776 [ERROR] Aborting

Thank you!
This helps

so it is true that this is a 4K sector disk with all different BytesPerSector values being 4096.

LogicalBytesPerSector : 4096 (<--- IO size need to be multiple of that)
PhysicalBytesPerSectorForAtomicity : 4096
PhysicalBytesPerSectorForPerformance : 4096
FileSystemEffectivePhysicalBytesPerSectorForAtomicity : 4096

I think if you cleanup C:\datadir (remove all files from there), it would startup now with --innodb_flush_log_at_trx_commit=2

Great news bro it works with: mysqld --datadir=C:\datadir --skip-grant-tables --innodb_flush_log_at_trx_commit=2 --console

but my question what should i do now?

That is up to your entirely. You can wait for the fix, which probably will be in 10.3.9 . If you are curious to try out currrent head of 10.3 + fix, I could build an MSI package, or ZIP for you.

yes please, if you can build an MSI that will be awesome

Here it is https://1drv.ms/u/s!AqT4tBcElQz_j4g75pDgGhtV-n0JWg , shared it on OneDrive

Thanks, But still i got this new problem:
"Service 'MySQL' (MySQL) failed to start. Verify that you have sufficient privileges to start system service." and my user is admin.

Did you install?

If this failed, coulld you collect installer logs? https://mariadb.com/kb/en/library/installing-mariadb-msi-packages-on-windows/#installation-logs describes how to.

here is the last few lines of the log and i attached the log file

Action 4:47:38: CreateShortcuts. Creating shortcuts
MSI (s) (7C:5C) [04:47:38:928]: Executing op: SetTargetFolder(Folder=23\MariaDB 10.3 (x64))
MSI (s) (7C:5C) [04:47:38:928]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs
MSI (s) (7C:5C) [04:47:38:928]: Executing op: ShortcutCreate(Name=hjcjcpxn|my.ini (MariaDB 10.3 (x64)),,,FileName=C:\Windows\system32\notepad.exe,Arguments="C:\Program Files\MariaDB 10.3\data\my.ini",,,,,,Description=Edit database configuration,,,,)
CreateShortcuts: Shortcut: hjcjcpxn|my.ini (MariaDB 10.3 (x64))
MSI (s) (7C:5C) [04:47:38:928]: Note: 1: 1402 2: HKEY_CLASSES_ROOT\.3 (x64)) 3: 2
MSI (s) (7C:5C) [04:47:38:951]: Executing op: ShortcutCreate(Name=moc4xjbe|Error log (MariaDB 10.3 (x64)),,,FileName=C:\Windows\system32\notepad.exe,Arguments="C:\Program Files\MariaDB 10.3\data\DESKTOP-73DO6HI.err",,,,,,Description=View Database Error log,,,,)
CreateShortcuts: Shortcut: moc4xjbe|Error log (MariaDB 10.3 (x64))
MSI (s) (7C:5C) [04:47:38:951]: Note: 1: 1402 2: HKEY_CLASSES_ROOT\.3 (x64)) 3: 2
MSI (s) (7C:5C) [04:47:38:951]: Executing op: ShortcutCreate(Name=iopypstq|Database directory (MariaDB 10.3 (x64)),,,FileName=C:\Program Files\MariaDB 10.3\data\,,,,,,,,,,,)
CreateShortcuts: Shortcut: iopypstq|Database directory (MariaDB 10.3 (x64))
MSI (s) (7C:5C) [04:47:38:951]: Note: 1: 1402 2: HKEY_CLASSES_ROOT\.3 (x64)) 3: 2
MSI (s) (7C:5C) [04:47:38:951]: Executing op: ShortcutCreate(Name=4rwooyg8|MySQL Client (MariaDB 10.3 (x64)),,,FileName=C:\Windows\system32\cmd.exe,Arguments=/k " "C:\Program Files\MariaDB 10.3\bin\mysql.exe" "--defaults-file=C:\Program Files\MariaDB 10.3\data\my.ini" -uroot -p",WorkingDir=C:\Program Files\MariaDB 10.3\bin\,,,,,Description=Starts mysql.exe for root user,,,,)
CreateShortcuts: Shortcut: 4rwooyg8|MySQL Client (MariaDB 10.3 (x64))
MSI (s) (7C:5C) [04:47:38:951]: Note: 1: 1402 2: HKEY_CLASSES_ROOT\.3 (x64)) 3: 2
MSI (s) (7C:5C) [04:47:38:951]: Executing op: ShortcutCreate(Name=sovdb45c|Command Prompt (MariaDB 10.3 (x64)),,,FileName=C:\Windows\system32\cmd.exe,Arguments=/k "set MYSQL_HOME=C:\Program Files\MariaDB 10.3\data\&& set PATH=C:\Program Files\MariaDB 10.3\bin\;%PATH%;&&echo Setting environment for MariaDB 10.3 (x64) ",,,,,,Description=Opens command line in the installation bin directory,,,,)
CreateShortcuts: Shortcut: sovdb45c|Command Prompt (MariaDB 10.3 (x64))
MSI (s) (7C:5C) [04:47:38:951]: Note: 1: 1402 2: HKEY_CLASSES_ROOT\.3 (x64)) 3: 2
MSI (s) (7C:5C) [04:47:38:951]: Executing op: ActionStart(Name=WriteRegistryValues,Description=Writing system registry values,Template=Key: [1], Name: [2], Value: [3])
Action 4:47:38: WriteRegistryValues. Writing system registry values
MSI (s) (7C:5C) [04:47:38:951]: Executing op: ProgressTotal(Total=16,Type=1,ByteEquivalent=13200)
MSI (s) (7C:5C) [04:47:38:951]: Executing op: RegOpenKey(Root=-2147483647,Key=Software\MariaDB 10.3 (x64)\Uninstall,,BinaryType=1,,)
MSI (s) (7C:5C) [04:47:38:951]: Executing op: RegAddValue(Name=shortcuts,Value=1,)
WriteRegistryValues: Key: \Software\MariaDB 10.3 (x64)\Uninstall, Name: shortcuts, Value: 1
MSI (s) (7C:5C) [04:47:38:951]: Executing op: RegAddValue(Name=shortcuts.commandline,Value=1,)
WriteRegistryValues: Key: \Software\MariaDB 10.3 (x64)\Uninstall, Name: shortcuts.commandline, Value: 1
MSI (s) (7C:5C) [04:47:38:966]: Executing op: RegAddValue(Name=shortcuts.commandprompt.db,Value=1,)
WriteRegistryValues: Key: \Software\MariaDB 10.3 (x64)\Uninstall, Name: shortcuts.commandprompt.db, Value: 1
MSI (s) (7C:5C) [04:47:38:966]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWARE\MariaDB 10.3 (x64),,BinaryType=1,,)
MSI (s) (7C:5C) [04:47:38:966]: Executing op: RegAddValue(Name=DATADIR,Value=C:\Program Files\MariaDB 10.3\data\,)
WriteRegistryValues: Key: \SOFTWARE\MariaDB 10.3 (x64), Name: DATADIR, Value: C:\Program Files\MariaDB 10.3\data\
MSI (s) (7C:5C) [04:47:38:966]: Executing op: RegAddValue(Name=InstalledBy,Value=DESKTOP-73DO6HI\Moh'd N. Alfayez,)
WriteRegistryValues: Key: \SOFTWARE\MariaDB 10.3 (x64), Name: InstalledBy, Value: DESKTOP-73DO6HI\Moh'd N. Alfayez
MSI (s) (7C:5C) [04:47:38:966]: Executing op: RegAddValue(Name=SERVICENAME,Value=MySQL,)
WriteRegistryValues: Key: \SOFTWARE\MariaDB 10.3 (x64), Name: SERVICENAME, Value: MySQL
MSI (s) (7C:5C) [04:47:38:966]: Executing op: RegAddValue(Name=STDCONFIG,Value=1,)
WriteRegistryValues: Key: \SOFTWARE\MariaDB 10.3 (x64), Name: STDCONFIG, Value: 1
MSI (s) (7C:5C) [04:47:38:966]: Executing op: RegAddValue(Name=UTF8,Value=1,)
WriteRegistryValues: Key: \SOFTWARE\MariaDB 10.3 (x64), Name: UTF8, Value: 1
MSI (s) (7C:5C) [04:47:38:966]: Executing op: RegAddValue(Name=INSTALLDIR,Value=C:\Program Files\MariaDB 10.3\,)
WriteRegistryValues: Key: \SOFTWARE\MariaDB 10.3 (x64), Name: INSTALLDIR, Value: C:\Program Files\MariaDB 10.3\
MSI (s) (7C:5C) [04:47:38:966]: Executing op: RegOpenKey(Root=-2147483646,Key=Software\Microsoft\Windows\CurrentVersion\Uninstall\MariaDB 10.3 (x64),,BinaryType=1,,)
MSI (s) (7C:5C) [04:47:38:966]: Executing op: RegAddValue(Name=DisplayName,Value=MariaDB 10.3 (x64),)
WriteRegistryValues: Key: \Software\Microsoft\Windows\CurrentVersion\Uninstall\MariaDB 10.3 (x64), Name: DisplayName, Value: MariaDB 10.3 (x64)
MSI (s) (7C:5C) [04:47:38:966]: Executing op: RegAddValue(Name=Publisher,Value=MariaDB Corporation Ab,)
WriteRegistryValues: Key: \Software\Microsoft\Windows\CurrentVersion\Uninstall\MariaDB 10.3 (x64), Name: Publisher, Value: MariaDB Corporation Ab
MSI (s) (7C:5C) [04:47:38:966]: Executing op: RegAddValue(Name=DisplayVersion,Value=10.3.8.0,)
WriteRegistryValues: Key: \Software\Microsoft\Windows\CurrentVersion\Uninstall\MariaDB 10.3 (x64), Name: DisplayVersion, Value: 10.3.8.0
MSI (s) (7C:5C) [04:47:38:966]: Executing op: RegAddValue(Name=InstallLocation,Value=C:\Program Files\MariaDB 10.3\,)
WriteRegistryValues: Key: \Software\Microsoft\Windows\CurrentVersion\Uninstall\MariaDB 10.3 (x64), Name: InstallLocation, Value: C:\Program Files\MariaDB 10.3\
MSI (s) (7C:5C) [04:47:38:966]: Executing op: RegAddValue(Name=UninstallString,Value=msiexec.exe /I

MSI (s) (7C:5C) [04:47:38:966]: Executing op: RegAddValue(Name=MajorVersion,Value=10,)
WriteRegistryValues: Key: \Software\Microsoft\Windows\CurrentVersion\Uninstall\MariaDB 10.3 (x64), Name: MajorVersion, Value: 10
MSI (s) (7C:5C) [04:47:38:966]: Executing op: RegAddValue(Name=MinorVersion,Value=3,)
WriteRegistryValues: Key: \Software\Microsoft\Windows\CurrentVersion\Uninstall\MariaDB 10.3 (x64), Name: MinorVersion, Value: 3
MSI (s) (7C:5C) [04:47:38:966]: Executing op: ActionStart(Name=WriteIniValues,Description=Writing INI files values,Template=File: [1], Section: [2], Key: [3], Value: [4])
Action 4:47:38: WriteIniValues. Writing INI files values
MSI (s) (7C:5C) [04:47:38:966]: Executing op: ProgressTotal(Total=2,Type=1,ByteEquivalent=13200)
MSI (s) (7C:5C) [04:47:38:966]: Executing op: IniFilePath(File=my.ini,Folder=C:\Program Files\MariaDB 10.3\data)
MSI (s) (7C:5C) [04:47:38:966]: Executing op: IniWriteRemoveValue(Section=mysqld,Key=innodb_buffer_pool_size,Value=2035M,Mode=1)
WriteIniValues: File: my.ini, Section: mysqld, Key: innodb_buffer_pool_size, Value: 2035M
MSI (s) (7C:5C) [04:47:38:966]: Executing op: IniWriteRemoveValue(Section=mysqld,Key=character-set-server,Value=utf8,Mode=1)
WriteIniValues: File: my.ini, Section: mysqld, Key: character-set-server, Value: utf8
MSI (s) (7C:5C) [04:47:38:982]: Executing op: ActionStart(Name=ExecSecureObjects_64,,)
Action 4:47:38: ExecSecureObjects_64.
MSI (s) (7C:5C) [04:47:38:982]: Executing op: CustomActionSchedule(Action=ExecSecureObjects_64,ActionType=11265,Source=BinaryData,Target=*********,CustomActionData=*********)
MSI (s) (7C:6C) [04:47:38:982]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI79A1.tmp, Entrypoint: ExecSecureObjects
MSI (s) (7C:B4) [04:47:38:982]: Generating random cookie.
MSI (s) (7C:B4) [04:47:38:982]: Created Custom Action Server with PID 7864 (0x1EB8).
MSI (s) (7C:AC) [04:47:38:998]: Running as a service.
MSI (s) (7C:AC) [04:47:38:998]: Hello, I'm your 64bit Elevated Non-remapped custom action server.
MSI (s) (7C:5C) [04:47:39:029]: Executing op: ActionStart(Name=StartServices,Description=Starting services,Template=Service: [1])
Action 4:47:39: StartServices. Starting services
MSI (s) (7C:5C) [04:47:39:029]: Executing op: ProgressTotal(Total=1,Type=1,ByteEquivalent=1300000)
MSI (s) (7C:5C) [04:47:39:029]: Executing op: ServiceControl(,Name=MySQL,Action=1,Wait=1,)
StartServices: Service: MySQL

and i attached the screenshoot of the error when starting the services from MSI

Thanks, very helpful.

Indeed, I missed something in my patch, now hopefully fixed.
I updated https://1drv.ms/u/s!AqT4tBcElQz_j4g75pDgGhtV-n0JWg with the new MSI. If you can test it, thatd be great.

GREAT NEWS

Its successfully installed and work perfectly

Thank you so much