How to uninstall Youku on Windows

Save wanted files and settings before removing Youku 9.2.66.1001 on Windows. The locations below were observed in this test; keep shared components separate from app data.

Use the app's uninstaller

Quit Youku, then uninstall it from Settings › Apps › Installed apps. Save wanted downloads and settings first.

Data and remaining locations

Enter each complete path in File Explorer. Copy wanted data and settings first; unused caches can be removed. Keep drivers, shared parent folders and shared registrations.

Check the result

Get-Process YOUKU,YoukuNplayer -ErrorAction SilentlyContinue
Test-Path "${env:ProgramFiles(x86)}\YOUKU\9.2.66.1001"
Test-Path "$env:APPDATA\youku"
Test-Path "$env:APPDATA\youku-app"
Test-Path 'HKCU:\SOFTWARE\YouKu\YoukuClient'
Test-Path 'HKCU:\SOFTWARE\YouKu\YoukuElec'
Test-Path 'HKCU:\SOFTWARE\YouKu\iKuAcc'
Test-Path 'HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Youku'
winget list --id Youku.Youku --exact

Test-Path returns True if that exact path exists and False if it is absent; True is expected for data you kept. Resolve query errors before drawing a conclusion. If a process, service or app query lists this product, check its path and installation source. Empty output with suppressed errors alone does not prove removal.

If you installed it with winget

These commands invoke the vendor uninstaller. This test used Mole and did not repeat removal separately through winget.

winget uninstall --id Youku.Youku --exact

What Mole lists

The two Youku data folders and three product settings keys are listed but not selected by default. Selected registry settings are backed up first. AlibabaProtect, xcdn and other shared SDKs are not removed with this app.

What this test covered

Tested on October 5, 2026, in a Windows 11 ARM64 VM with a Mole development build, covering first launch and uninstall. Sign-in, offline downloads, settings recovery or a second installed-app review, other installation channels and the released download were not verified. Automatic detection after an external uninstall was not verified.

The three settings keys were removed in a focused retest after the rules were added. The full revised review was not verified after another installation. Shared SDK contents remained.