Right Click context menu no show HD Video files


  1. Posts : 6
    Windows 10
       #1

    Right Click context menu no show HD Video files


    I have many Video files on PC
    Some are large files (5gb) High Definition Movies
    Movies have been recorded from TV using topfield PVR
    Most are 1920 x 1080 resolution some have 2 channel audio some have 6 channel audio
    Also have some standard definition movies
    I have just got a Windows 10 PC and now having problems with some files that will not show the context menu when right clicked
    The process starts but then will just churm away for as long as I care to wait
    If I click again it just whites out and freezes
    It seems all the standard definition files and the HD files with only 2 channel audio work fine
    The problem appears to be with only the HD movies that have 6 channel audio
    These are movies recorded from only 2 different TV channels
    These problem files work perfectly on any pc with Windows 7
    If I reduce the size of these files (Cut large amounts from the movie) they will sometimes show the context menu after about 10 seconds or so.
    I have taken these files to 2 separate windows 10 pc's at my work place and the problem is still present.
    Sorry about the long explanation but I figured more info is better than less
    Hope somebody out there might have some suggestions or solutions to this annoying problem
    Thanks
      My Computer


  2. Posts : 34,829
    Win 10 Pro (1903) (2nd PC is 21H2)
       #2

    Hi, the usual way to identify context menu problems is to
    a. disable all shell extensions and check again
    b. if the context menu displays of and explorer doesn't crash, enable in groups or in turn to identify rogue extensions.

    Tools: (ensure you hide all MS extensions)
    e.g. Shellexview (free)
    more extensions: Autoruns (free) (can be daunting to the inexperienced).
      My Computers


  3. Posts : 6
    Windows 10
    Thread Starter
       #3

    Thanks dalchina i will try your suggestions
      My Computer


  4. Posts : 6
    Windows 10
    Thread Starter
       #4

    Would it be likely that the same rogue extensions would be on three different windows 10 computers
      My Computer


  5. Posts : 34,829
    Win 10 Pro (1903) (2nd PC is 21H2)
       #5

    If
    a. what you're seeing has anything to do with a shell extension
    b. you have the same prog or progs giving rise to the same symptom installed on each

    What you're encountering might be something different.
    The process starts but then will just churm away for as long as I care to wait
    What you might try doing is
    a. launch the task manager
    b. rt click a file giving the symptom
    c. observe the task manager - perhaps there will be a process with high CPU/Disk use that will help you see what's happening.
      My Computers


  6. Posts : 6
    Windows 10
    Thread Starter
       #6

    Thanks again dalchina
    Will try all this when i get home from work tonight
      My Computer


  7. Posts : 6
    Windows 10
    Thread Starter
       #7

    Thanks for all your help
    Tried everything problem is not with PC
    Problem is with Windows 10
    Have now tried the files on two more totally unrelated windows 10 computers and same thing happens
    Also happens on Windows 8 Computer
    Will now be scrapping Windows 10 and going back to Windows 7
      My Computer


  8. Posts : 34,829
    Win 10 Pro (1903) (2nd PC is 21H2)
       #8

    Please take moment to report this and your frustration with Win 10 using the Feedback Hub app.

    I'm staying with build 1709- two builds back- so many problems with 1803 and now 1809. Seems MS has lost the plot.
      My Computers


  9. Posts : 6
    Windows 10
    Thread Starter
       #9

    Thanks dalchina
    Have put in the report
    How would I get back to build 1709 ?
      My Computer


  10. Posts : 34,829
    Win 10 Pro (1903) (2nd PC is 21H2)
       #10

    Thanks.

    The only way to go back to an earlier major build after more than 10 days from upgrading is

    a. Clean install
    b. Restore a disk image of that build
    c. Use a clone of that build

    Of course there's no guarantee 1709 would not demonstrate the same problem... but you could try it.

    You'd need a 1709 iso - freely downloadable. E.g. iso tool, post #3 after Kyhi's boot disk, thread at the top of the Software and Apps section.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:09.
Find Us




Windows 10 Forums