Announcing Windows 10 Insider Preview Slow Build 17074.1002 - Jan. 11 Insider

f14tomcat said:

@RFHavens

That looks suspiciously like what is reported in Known Issues. At 75%, it tries to re-boot, gets a little of the BIOS screen, then totally blank and just sits. Power off/on and it rolls back. I had that on 17063 as well. Read the Blog and these notes first this time, and saw the Known Issue and workaround. I let it try to upgrade, and at 75%, it hung and rolled back. I went into BIOS and disabled virtualization and booted. Let the update start again and it went thru totally ok. At 75%, it booted normally and finished with all the "Hi!" stuff and a desktop.

---

Excerpt from release notes (Page #1 this post)

Certain devices may hang on the boot screen after upgrading. If this happens to you, go into the BIOS and disable virtualization.

---

If that is your case, you may be able to see if virtualization is currently enabled by looking at the CPU data in the Performance tab of Task Manager. I have mine disabled for now.

Attachment 172637

I have had it disabled since trying to get 17063 installed. I am just leaving it off. I haven't had to power off as my laptop just restores after the 2nd reboot. I am remaining optimistic that if not this release maybe a future one will finally install. Thanks for the suggestions though.

johngalt said:

That is the way it is designed. If you make it double arrow resizing on top or bottom edge and bump to an edge, top or bottom, it maximizes height only to your screen.

Grabbing the title bar of an app and dragging up to top edge maximizes.

johngalt said:

I finally figured out what you were doing, and it seems as if this is by design, because it did it on my machines as well.

Solution: Manually make window the size of the height of your screen by grabbing title bar and dragging *down* so bottom edge is just off screen, then grabbing top edge and stretching up until just before you hit top edge, then grabbing title bar again and moving it up just a little too bring bottom edge back into view.

Takes some practice, but you can have a window occupying the entire height of your monitor without actually maximizing it to your monitor height, and then it will stay at that size through app restart.

Thanks, but I'm not a mouser, so one technique new to me. I knew about snap way back in 7 with keyboard shortcuts and mouse technique except the dbl-arrow snap top to bottom (not side). I don't use resizing or moving around. Sometimes I'll use the the side-by-side snapping with KB SCs, but not much since I dual-monitor. I'm also retired and I don't do that muck work on a PC any longer.

So what you're saying is that it's the double-arrow sizing that sets the x/y size of a window to be recorded for next use. Not just grabbing by the menu/title bar and moving the window down. One has to use the dbl arrow.

BTW, in doing a little research, some of the sizes are recorded in the Registry while some are recorded in the app itself.

So far as the .old folder; The cleaner in Storage Sense cleans/deletes it all for me.

Settings > System > Change how we free up space > Clean now.

However, since I dual-boot with a smaller SSD, it usually asks me if I want to clean the old folder, but for some reason after this update it didn't. Went in and did it manually.

johngalt said:

Yes, and no.

If you use the double arrow, but take it to the top (or bottom) edge of the screen (depending upon whether you stay at the top or bottom edge of the screen) it will maximize the hurt only of the app, keep the width the same as when you started.

However, when you do this, then closer the so, instead of remembering that particular size, the app opens completely maximized then next time it opens, which is not what most expect it to do, and frankly, counterintuitive.

Using the Winkey+arrow key shortcuts to maximize height also causes the so to open fully maximized when you open it again later, unless you cycle through the shortcut until it placed the so in the middle of the screen with being clipped to any border.

Convoluted, eh?

One window that you have to do this with, now that I think about it, is Task Manager. Task Manager will never remember maximized state, no matter what the settings! It tries to, but it won't!