Windows 10: Bugs of build 15019 Solved

  1. Posts : 22
    Windows 10 insider preview 14986
       29 Jan 2017 #1

    Bugs of build 15019

    Let's try to write a list of all bugs discovered in build 15019.

    If you experienced something, pls help us to fill the list. If you found solutions, pls share.

    Here the first bugs I experienced:

    - Action center becoming transparent, with no content inside. Still not solved.
    - Start up Log in PIN cannot be used anymore. I have to log in with password. Settings for PIN disabled.
      My ComputerSystem Spec

  2. Posts : 94
    Always the latest Insider build.
       29 Jan 2017 #2

    Two bugs on my two Windows 10 15019 computers: (1) Safe Mode does not work....get a screen with no icons and the shakes (2) DISM "Restore Health" won't complete because it can not find a file.
      My ComputerSystem Spec

  3. Posts : 70
    windows 10 Insider Preview 16179
       01 Feb 2017 #3

    my bugs in build 15019

    try to bookmark in chrome choosing a different folder hangs and does nothing

    touchpad over sensitive sends cursor all over even when nothing is touching it

    sound drivers stopped working reverted to generic which have no controls and sound awful

    keyboard sticks constantly

    cannot add Chrome extensions (app freezes)

    Explorer folder and browser windows constantly freeze. pressign Esc unfreezes but no commands work. you can close the window though

    cant install programs
      My ComputerSystem Spec

  4. slicendice's Avatar
    Posts : 3,443
    Windows 10 Pro x64 v1803 Build 17134.228 (Branch: RS4 Release Preview)
       01 Feb 2017 #4

    Only bug I have found so far is that when I write a reply in this forum using Edge, sometimes I get the* "*"-character instead of "SPACE"-character.

    EDIT: as you can see to be proven in this post also*
      My ComputersSystem Spec

  5.    02 Feb 2017 #5

    TBH I do not see much point in this as new builds come out so fast now, and bugs are usually random ie some get it and others do not.

    What is more useful is if a user gets a bug and can give a workaround.

    Really users should use the feedback hub if they get a bug providing as much info eg pc, graphics etc.
      My ComputerSystem Spec

  6.    02 Feb 2017 #6

    Probably the worst bug of Build 15019 is that Build 15025 is right behind it!!!
      My ComputerSystem Spec

  7.    02 Feb 2017 #7

    Edwin said: View Post
    Probably the worst bug of Build 15019 is that Build 15025 is right behind it!!!
    And that is my point - builds come up so fast, keeping track of bugs is an impossible task. People will be reporting bugs on 15019 that may well have been fixed on 15025, and new bugs on 15025, then a few days later with next build.

    Of course if some person is willing to do that and manage a list (not just a bunch of posts), then fine. Reality, is it takes an organisation the size of MS to do this.

    Even then, it is a statistical process ie the bug would have to have been reported many times, and perhaps more importantly, the bug has to be reproducable by MS ie they have to sift bugs caused by incorrect coding from those where installs may be corrupted etc.

    I always try a repair upgrade first before reporting a bug on feedback, as I find this sorts most issues.

    No disrepect intended to OP, but i have seen similar initiatives on other forums and they always get abandoned after a few days as thare are just too many variables.

    As I said what is potentially useful is if a person finds a bug (and preferably tried a repair upgrade), and comes up with a solution or workaround e.g. one bug at the moment is you cannot track the download process on some installs.

    I got this issue and my workaround was simple - I just viewed the c:\windows\softwaredistribution folder in file explorer, checking the folder properties periodically, so i could tell when approx 3GB of stuff was downloaded. OK not precise but gave me a feel if it was going to be 30 mins, 1 hr, 2hrs etc. before the download finished.
      My ComputerSystem Spec

  8. Posts : 70
    windows 10 Insider Preview 16179
       13 Feb 2017 #8

    I]I always try a repair upgrade first before reporting a bug on feedback, as I find this sorts most issues.[/I]

    The quote above is from Cereberus who I would like to ask how to do a repair upgrade on a preview build.

    I have been unable to access any support through the Action Center and going to proves to be frustrating as any suggestions from that site is very vague and often times unrelated to my question.

    Since build 15025 I have been unable to access the Windows Store (restoring System Health has not worked either), Feedback Hub, Support, I am unable to install extensions in Chrome, most applications not available through the Windows Store, and so many more...also, my first attempt at fixing problems with build 15019 which I listed in this thread I was instructed to reset my windows installation which then made it impossible to roll back the installation later when that was suggested and is what I would like to do now!

    so it seems like a repair install may be what I need but I am just not sure how to do it.

    I am running windows 10 Insider preview 15031 on a Dell Studio 1745 laptop

      My ComputerSystem Spec

  9. slicendice's Avatar
    Posts : 3,443
    Windows 10 Pro x64 v1803 Build 17134.228 (Branch: RS4 Release Preview)
       14 Feb 2017 #9

    @djrobison22 , try THIS tutorial by Brink.
      My ComputersSystem Spec

  10.    14 Feb 2017 #10

    Of course, to do a repair upgrade, it is necessary to create an iso before installing the Insider versions (see tutorials).
      My ComputerSystem Spec


Related Threads
825063872533032960 825065215523971072 825213100613775360 Source:
When I click on a text field in a web page, Edge shows a list box with responses I've previously entered in similar fields. In previous builds, I could click on one of the choices and the text box would be filled with that value. In Build 15019, the...
This is amazing. Printers autodetection still doesn't work under new 14393.10 w10 build. :eek::shock: MS had a whole year to fix it.
Admins please delete
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 19:48.
Find Us