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

Previously used disc clean-up to remove .old,
however for the last 5 builds it has not removed the FOLDER internal data yes. via properties 0 bytes

So i just used the take ownership/ delete folder commands

ALL gone

Roy

Tony K said:

Thanks, Andre. I see what you mean now. I set mine like that and it reopens the same every time. It's a mystery as to why you can't. I do believe window sizes are recorded in the Registry. Not sure.

If you work the way you describe, may I suggest to keep your Taskbar at the left to access open programs and programs. You can then leave windows full.

---

Strange thing I noticed about snapping is grabbing a window by its menu bar and bumping it up to the top snaps it full as it should, but grabbing the bottom most part when pointer turns to double arrow and bumping it down snaps it from top to bottom, but not side to side. After doing that it opens full screen next time opened, though.

Anywho, so much for using the mouse. You know how I feel about that. Keyboard is so much easier for me. WinKey/Tab for Timeline now or Alt/Tab.



Attachment 172590

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.

AndreTen said:

no, sorry to mix this in Insider thread.. It's the same in FCU..

Should made separate thread, so no need to take this further. Just wanted to know, if it's common to others, since I'm kinda waiting in every new build to be fixed.

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.

smactilactus said:

Like Wynona, I must have been lucky with my the computer I built, as I rarely if ever have any of the problems I read about on here. I have played with Edge, and it comes back the exact same size, and in the same place I left it every time. Every time I read of any problem anyone on here has, I go and test the exact same thing, and just don't seem to have the same experiences .
Although I do experience some flaky behavior from these builds sometimes, which is to be expected with test builds.

You have to replicate the maneuver he is doing in order to see it manifest.

Fast way:. Open edge, use Winkey + right arrow to move it to the right side of your monitor. Now close edge and open it again.

LEOPEVA64 said:

The problem is not only Edge, at least in my case, it happens in other apps such as Photos, Mail, Maps etc and it is quite annoying for me, a few months ago, when I made this comment, I was referring precisely to this problem:

Oh, I can see that now. Not working with those apps often, if sized top to bottom. So it looks like it's a Modern apps problem?

RFHavens said:

Thanks Tony. Still no joy. I did everything I could find in the articles and then ran from the ISO again. Here is the complete error that showed up after it failed this time:

We couldn't install Windows 10
We set the PC back

0xC1900101-0x40017
The installation failed in the SECOND_BOOT phase with an error during BOOT operation.

I ran sfc /SCANNOW and had zero errors.

@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.