-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows 10 Enterprise 2016 #14339
Labels
Comments
ah jah, in case youre asking here are some app-crash-event-logs from that machine in question: mpv appcrash win 10 enterprise 2016.zip |
Your CPU does not support AVX2, download |
tried that to, same error with latest version
…________________________________________
Von: Kacper Michajłow ***@***.***>
Gesendet: Dienstag, 11. Juni 2024 13:43
An: mpv-player/mpv
Cc: lhpitn; Author
Betreff: Re: [mpv-player/mpv] Windows 10 Enterprise 2016 (Issue #14339)
Your CPU does not support AVX2, download mpv-x86_64- package. (non-v3)
—
Reply to this email directly, view it on GitHub<#14339 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AK5KY7P7ZVH2G5ID6CCCZ73ZG3PFTAVCNFSM6AAAAABJEEYXQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRQGU2TAOBQGQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
i tried at least 5 versions until i found that one that was working, first from the v3 folder then from the other one, unfortunately i cleaned up my download folder afterwards, if you think it may help ill try some more and give you the results but i would appreciate some hints where major changes have been made for doing it more systematicly then just scrolling and clicking randomly...
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
mpv Information
Other Information
Reproduction Steps
try to run latest mpv.exe on Windows 10 Enterprise 2016 LTSB 64-bit (10.0, Build 14393) (14393.rs1_release.190503-1820)
Expected Behavior
working
Actual Behavior
error
Log File
dosnt start
Sample Files
i checkt all that even tho they dont apley all to my situation, please mind that when making filelds forced
I carefully read all instruction and confirm that I did the following:
--log-file=output.txt
.The text was updated successfully, but these errors were encountered: