New Windows 10 Insider Preview Fast Build 18312 (19H1) - Jan. 9 Insider

Page 17 of 30 FirstFirst ... 7151617181927 ... LastLast

  1. Posts : 2,491
    Windows Insider Fast Ring LatestKUuuntu 20.10
       #160

    Doing a reset on Windows 10 Enterprise. Haven't done that for quite awhile. We will see if that helps - otherwise I'I will try a complete reset - otherwise I guess I can get a trial version of Enterprise 1809 somewhere from MS.
      My Computers


  2. Posts : 1,778
    Windows 10 Pro,
       #161

    martyfelker said:
    You have seen BSOD I assume. Well you can always same a Blue Screen Image (espeically from a VM) and use Paint to change the color to green.

    OK, I get it. Not as exciting as I thought.
      My Computer


  3. Posts : 3,352
    Windows 10 Pro x64
       #162

    jimbo45 said:
    I don't believe Ms is The Evil Empire -- I just feel somehow the people at the top have got their wires a bit crossed -- they need to get bac and have a sensible future ongoing policy so consumers etc know where they are heading. Having around 7 different builds in the last 3 or 4 months IMO is totally bonkers confusing consumers and developers alike and that's where management at the top needs to take a grip.
    I don't think they are the Evil Empire either, but I do believe they have more than a touch of arrogance. They have long seemed to think they know better what we need than we do ourselves. What Microsoft really should do is pay more attention what what users actually want. It would save them from working so hard on pie-in-the-sky features few want and will have any use for.
      My Computer


  4. Posts : 68,894
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       #163

    Odd. I just got the screen below after signing in to my account for build 18312.

    This wasn't right after updating to build 18312. This was after shutting down and sign out/in several times today since.

    New Windows 10 Insider Preview Fast Build 18312 (19H1) - Jan. 9-setup.jpg
      My Computers


  5. Posts : 2,491
    Windows Insider Fast Ring LatestKUuuntu 20.10
       #164

    Yeah. This is a bizarre update. I do believe my Windows 10 Enterprise is a lost cause and am frankly amazed that Windows for Workstations VM was able to upgrade.
      My Computers


  6. Posts : 3,453
       #165

    Brink said:
    Odd. I just got the screen below after signing in to my account for build 18312.

    This wasn't right after updating to build 18312. This was after shutting down and sign out/in several times today since.

    New Windows 10 Insider Preview Fast Build 18312 (19H1) - Jan. 9-setup.jpg
    Hmmmm... that's interesting Shawn... a bit "bullish" but nevertheless, part of the cloud-centricity I suppose.

    A notification would be a better option.. ... ..... IMHO
      My Computer


  7. Posts : 2,491
    Windows Insider Fast Ring LatestKUuuntu 20.10
       #166

    Just made a Virtualbox 6.0 from the 18321 and got a really screwed up Start menu. These two screenshots don't convey the weirdness involved - for example deleting one of the duplicate tabs deletes the other etc etc. This was an install using a valid key and with a new MS account. I would be interested in any other experiences of installing from a 18321 ISO - anybody out there??New Windows 10 Insider Preview Fast Build 18312 (19H1) - Jan. 9-virtualbox_windows-10-insider-preview_11_01_2019_01_13_00.pngNew Windows 10 Insider Preview Fast Build 18312 (19H1) - Jan. 9-virtualbox_windows-10-insider-preview_11_01_2019_01_16_52.png
      My Computers


  8. Posts : 4,666
    Windows 10 Pro x64 21H1 Build 19043.1151 (Branch: Release Preview)
       #167

    @Brink

    I've had that glitch happen to me a few times (2-3) in the past. I don't remember which builds though. This build I can't even get installed.
      My Computers


  9. Posts : 2,491
    Windows Insider Fast Ring LatestKUuuntu 20.10
       #168

    I'll lay odds that this is the cause of some of 183312's weirdness - particularly the rebooting issue.
    This was posted on ZDNet.
    -----------------------------------------------------

    The latest Windows 10 Insider build, number 18312, introduces a new feature wherein the operating system reserves a big old chunk of disk space, effectively expanding its on-disk footprint by another 7GB.
    The storage reservation is to ensure that certain critical operations—most significantly, installing feature updates—always have enough free space available. Windows requires substantial extra disk space both during the installation of each feature update (as it unpacks all the files) and afterward (as the previous version of Windows is kept untouched, so that you can roll back if necessary). Lack of free space is one of the more common reasons for updates failing to install, so Microsoft is setting space available on a long-term basis, allowing those periodic updates to be sure they have what they need.
    The exact amount reserved will depend on the optional features and language packs installed, but about 7GB will be typical. The reserved space isn't entirely lost during normal usage, with certain temporary files having their disk usage charged against reserved space rather than free space. Being temporary, such files can be safely discarded each time an update is available to reinstate the full reserved capacity.
    The reservation itself is implemented within the NTFS file system. Each file system can have a reservation set, and free disk space will drop by the size of the reservation. Files created for Windows updates are marked specially, allowing their space usage to be charged against the reservation rather than regular free space. It isn't yet clear if the ability to create reservations will be a general-purpose facility. Advanced file systems on some other platforms (such as ZFS in Solaris) include a general reservation facility that operates in a similar way to this update-specific system, so it's not impossible to imagine Microsoft generalizing the capability.
      My Computers


  10. Posts : 11,247
    Windows / Linux : Arch Linux
       #169

    Hi there

    On this build :

    In a VMWare VM after 2nd re-boot of the VM I can't start anything from the menu (Windows icon). Anything on the task bar though can start -- weird. Worked fine on initial boot after install.

    On a VM in KVM (Linux Host Hypervisor) it works although very laggy mouse and keyboard so not really useable until I sort out mouse / keyboard problem. This could be because I'm using an experimental Linux 4.20 latest kernel -- will try again with the standard kernel for the distro.

    I don't have enough faith in these latest builds to attempt to use on a "Real" machine yet though --they need to be a bit more stable and not offer what to me seems fairly trivial "features" while ignoring the proper functionality of a professional OS used for other things than Xbox, games, mobile phone connections etc -- nothing wrong with people who want to do those things but this is where perhaps Windows needs to be split - instead of HOME and PRO how about say Business and Consumer where business is a cross between enterprise, pro and workstation while consumer could have all the "gaming" / Xbox stuff and those rediculous store apps in it.

    Cheers
    jimbo
      My Computer


 

  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 18:10.
Find Us




Windows 10 Forums