Adding up to the answer above, it is the issue that is resolved after SQL Server 2012 release. Thus, updating the SSMS to the 2014 or higher versions genuinely resolves the issue.

Adding up to the answer above, it is the issue that is resolved after SQL Server 2012 release. This restore issue is derived from the log files. I have seen some comments saying that "even though restore with UI doesn't work, restoring with query works well". However, the only working solution for me was to update SQL Server Management Studio. For example, updating the SSMS to the 2014 or higher versions genuinely resolves the issue.