If you had problem after updating to Winver 1607 read this. Start menu don't work...

Discussion in 'Windows 10' started by lievre, Jan 18, 2017.

  1. lievre

    lievre MDL Senior Member

    Sep 18, 2012
    343
    72
    10
    #1 lievre, Jan 18, 2017
    Last edited: Jan 18, 2017
    If you had problem after updating to Windows version 1607 read this.

    Start menu not working, calculator won't open, store won't open, right clicking on taskbar icons not working, notification area would not open.

    Relax and don't play with the command prompt or power shell.

    I had all these issues after updating to version 1607. Every time i had to go back to version 1511.

    Every time :mad::hummer::rocket::bangin::devil::diespam:

    Here what i found and it is working.

    The fix which worked on 4 computers. Change the default monitor in the display settings.

    All the computers had dual screens. The issue seemed to be caused by which monitor card the default monitor was connected to. Theses computers have a vga display port on the motherboard and an add in card for the second monitor.
    The default monitor needed to be set to the monitor connected to add in card.
    Hope this helps someone.


    Lievre
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. lobo11

    lobo11 TOMAHAWK CHOP

    Feb 16, 2012
    6,584
    5,365
    210
    What is Winver 1607 and before version 1607 was 1511 I believe :D
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. rpo

    rpo MDL Expert

    Jan 3, 2010
    1,511
    1,570
    60
    Some PC manufacters disable the VGA port in the BIOS when a video card is added to the configuration.
     
  4. lievre

    lievre MDL Senior Member

    Sep 18, 2012
    343
    72
    10
    Yep Sorry version was 1511, my bad.

    Lievre
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. Hadron-Curious

    Hadron-Curious MDL Guru

    Jul 4, 2014
    3,725
    600
    120
    This is more or less an isolated case. Most Insiders are largely using single screen and having such problem and relating it to VGA issue with one of the screens can be very speculative. However, thank you for sharing your finding.
     
  6. T-S

    T-S MDL Guru

    Dec 14, 2012
    3,984
    1,331
    120
    Yepp... an isolated case that everyone faced....:D
     
  7. tli

    tli MDL Novice

    Mar 11, 2011
    13
    11
    0
    May or may not be an isolated case... let me add my two bits as to what I've learned from my experience recently. There seems to be major bugs with the Win 10 handling of multi-monitors setup and configurations. On one of my system (running version 1607), it's only using one monitor, but the display adapter card has both VGA and DVI outputs--cannot be disabled independently. Win 10 would seem to randomly recognize that display adapter as being two separate monitors, even though only the DVI port is used and connected to a single monitor, while the VGA port is unused and not connected at all. Thus, most every time (about 9 out of 10) when system cold boots, it would get the dreaded blank screen with just a blue rotating circle and the cursor in the middle of the screen and nothing else displayed. Apparently, Win 10 had defaulted the display functions to a secondary 'phantom/ghost' monitor. Several Win+P attempts--switching the display mode, would reveal that multi-monitors mode is in effect, but only one monitor is actually being detected and shown. Unsure if related but this issue seemed to have surfaced after Windows Office was installed. The system was working fine before then. Anyway, on this particular Win 10 system, in order for it to consistently recognize the sole default monitor, I'd to turn off Win 10's fast-startup option. FYI.
     
  8. Hadron-Curious

    Hadron-Curious MDL Guru

    Jul 4, 2014
    3,725
    600
    120
    Yeah! This your very statement is an oxymoron and it is a bit patronizing to say the least! I am coaxed to reply to it. :biggrin:
     
  9. T-S

    T-S MDL Guru

    Dec 14, 2012
    3,984
    1,331
    120

    Do you need that I post some links or your're able to use the forum search by yourself?
     
  10. LatinMcG

    LatinMcG Bios Borker

    Feb 27, 2011
    5,700
    1,600
    180
    #10 LatinMcG, Jan 18, 2017
    Last edited: Jan 18, 2017
    i also seen scaling issues with 125% or higher and clicking remote support doesnt click in proper location.

    black screen with mouse and win p shows menu for monitors.. but 1 mon only pluged in.

    winlogon.dll issues and pwd not working whether local or ms account... spins circle for 40 secs then kicks back out to pretty lock screen pic.

    then u get these bullsht articles saying ms recommends switching to w10 cause 7 is not as secure.. well newsflash to nadela! the win 10 has major fkin issues still

    but i will say i have w10 fresh install and working fine (due to i skipped the ms account straight local originally)
     
  11. Hadron-Curious

    Hadron-Curious MDL Guru

    Jul 4, 2014
    3,725
    600
    120
    Oh, please... It is of no utmost importance. I still think it is more or less an isolated case though. I am just kidding. :D
     
  12. T-S

    T-S MDL Guru

    Dec 14, 2012
    3,984
    1,331
    120
    Indeed. Win3.11 users never faced any problem with the start menu. It's isolated to a fraction of W10 users. The ones who never heard about Classic shell :D
     
  13. lievre

    lievre MDL Senior Member

    Sep 18, 2012
    343
    72
    10
    If you do a search on the net, you will see a lot of people having this problem.


    Lievre
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. lievre

    lievre MDL Senior Member

    Sep 18, 2012
    343
    72
    10

    Nop i completely disagree with you on that. There is a million post on this topic.


    Lievre
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    50,765
    108,505
    450
    But not all, i for one didn't have the problem, neither do i have a multiple monitor setup.

    On both my pc's and my wife's laptablet i never encountered the problems of black screens or couldn't right-click the taskbar.

    My mainsystem only has an onboard HDMI output (it's the only output) connected to my monitor with a HDMI>DVI adapter.

    My testpc has an old AMD VGA card (AMD Radeon HD6450) with one VGA D-Sub and one DVI connector.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. T-S

    T-S MDL Guru

    Dec 14, 2012
    3,984
    1,331
    120
    Not sure did you get what I wrote. It's called irony.;)
     
  17. T-S

    T-S MDL Guru

    Dec 14, 2012
    3,984
    1,331
    120
    What has to do that with the start menu problems?

    They surface because the corrupt tile DB, not because a multiple monitor setup or a "wrong" driver.
     
  18. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    50,765
    108,505
    450
    I replied at the OP.

    There were more problems mentioned, non of them occurred here.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  19. RJARRRPCGP

    RJARRRPCGP MDL Senior Member

    Feb 24, 2010
    300
    38
    10
    3.11 was Program Manager, lol. The start menu didn't exist...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  20. Carlos Detweiller

    Carlos Detweiller Emperor of Ice-Cream
    Staff Member

    Dec 21, 2012
    7,096
    8,456
    240
    No sh*t, Sherlock. :D

    For that very reason, we didn't have any problem with it! ;)

    But seriously, the Windows Start Menu always worked flawless until they first ripped it, then added that "modern" abomination back. :mad:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...