Installing Windows 10 via Windows Update works surprisingly well. However, such upgrade leaves you stuck with partition layout you might not like. Sometime best course is installing from scratch.
First step to prepare installation is getting .iso file and Microsoft always provides a way to do it. With Windows 10 it is Microsoft Media Creation Tool.
Second step is to prepare bootable USB drive. This step can be done by tools but, if you want UEFI boot, you want to do it manually. Most of tools currently available format disk as NTFS and that file system is not supported by UEFI boot process. Yes, most BIOSes still have support for legacy mode but you do lose some boot speed improvements and there are security implications.
In regards to UEFI do notice that it isn’t really important if your processor supports 64-bit OS or not - if your UEFI system is 32-bit you better install 32-bit Windows too. This weird situation of having 32-bit UEFI only with 64-bit capable processor often happens with Atom tablets. Just treat them as 32-bit system and you’ll be fine. On more capable laptops and desktops UEFI usually has support for both or rarely for 64-bit only. Rule of the thumb is to get 32-bit .iso if you are dealing with tablet and 64-bit otherwise.
Procedure is actually simple. Just write DISKPART on start screen and you will be greeted with security prompt after which you will have old-fashioned textual interface. In my case USB was disk 3 (you can deduce it based on size) but your case will probably differ. Double check which disk you are selecting because DISKPARTdoes destroy data:
DISKPART> LIST DISK
Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 476 GB 0 B *
Disk 1 Online 931 GB 0 B
Disk 2 Online 7168 MB 0 B
Disk ^^3^^ Online 7648 MB 0 B
DISKPART> SELECT DISK ^^3^^
Disk 3 is now the selected disk.
DISKPART> CLEAN
DiskPart succeeded in cleaning the disk.
DISKPART> CREATE PARTITION PRIMARY
DiskPart succeeded in creating the specified partition.
DISKPART> FORMAT FS=FAT32 QUICK
100 percent completed
DiskPart successfully formatted the volume.
DISKPART> ACTIVE
DiskPart marked the current partition as active.
DISKPART> EXIT
Assuming that your, newly created and empty, USB drive is under letter U: and your Windows installation disk is at W:, you can use XCOPY to transfer files. Press + to get a prompt where you can enter following command:
XCOPY W:*.* /e /f U:\
Last step is to boot machine while pressing <F2> (or some other key; <Del> used to be popular) to enter BIOS. Since boot is extremely fast, I always need a few attempts to get inside. :)
Depending on the BIOS, option might have a slightly different name but most of them have “Boot override” section somewhere. Your new UEFI USB drive should appear there. Just select it and boot should ensue.
Enjoy your clean installation.
PS: Same procedure actually works for any UEFI system - from Windows Vista onward.
For its 4.00 version QText has received major refactoring with almost 100 changes separating it from the previous release.
Visually it is easy to see where some time went as there is new application icon together with new high-resolution toolbar icons. Yes, QText had high-DPI support for some time now but that always meant dealing with blurry toolbar buttons. With new graphics you should be greeted with crisp graphics no matter which resolution you’re using. It was a long overdue improvement.
Due to its internal structure, detecting external changes in files was not always straightforward as it should have been. Due to this experience with DropBox or similar file syncing software was not ideal. Long hours have been put into this version to recognize many external changes. Whether it is simple file edit in another editor or folder rename, QText will have you covered.
Lastly there was a push to cleanup some of the old and annoying bugs. All these changes should make QText more comfortable to use.
As always, you can download new version directly or use built-in upgrade menu.
PS: Order of your tabs will be reset to alphabetic with this version. This is a one-time change. QText will continue remembering tab order once you (re)order them again.
Those more observant among you might have noticed there is a books tab up there. Yep, I am a published author now.
While both books are more of a reference material than what you would usually consider a book they did require quite a lot of work - especially getting formatting and publishing just right. Those interested in that aspect can view what raw sources looks like and what goes into making a proper e-book.
As I went through one of the many Windows 10 beta updates, my VMware Player started throwing “Error while powering on: Internal error.” After reboot everything started working again so I just assumed it was simply some fluke in the upgrade process. And then it happened again a bit later. This time a single restart didn’t help but it did start working after a few of them. Every restart was like a coin toss. It smelled like a race condition.
One of things I checked was status of VMware’s services. There I noticed that, although startup type was set to Automatic, VMware Authorization Service was not running at times. And I could match the times when it was not running with the error. Even better, error would disappear as soon as I would manually start that service. My best guess, based on observed behavior, was that VMware Authorization Service needed some other service to start beforehand. However, dependencies for that service were missing. All VMware’s service needed was a bit more time.
Fortunately, Windows has one great feature enabling just that ever since Windows Vista. All needed is to change startup type to Automatic (Delayed Start) and your service will wait a bit extra time before starting. Original idea of this feature was to alleviate system load at startup by postponing some tasks for just a bit later when CPU had a chance to breathe. But, as a side effect, we can be sure that pretty much all important system services are already up by the time delayed start kicks in.
Might not be an ideal solution but I had no issues with it.
PS: Proper solution would be to find the missing dependency and add it to service. But setting up dependencies is not an easy task and pretty much becomes just trial-and-error adventure unless you know the product on the source code level. Not worth it.
It was a long overdue task to release new MagiWOL. Changes have been small but noticeable.
Finally there is a high-DPI support with multiple icon sizes to make application presentable on all these new displays out there. If you use classic display only difference will be in what icons you see. But if you are using anything that makes Windows want to scale icons, you should be able to enjoy extra crispy icons.
Those using import functionality will be happy that, beside ranges, now you can defined network subnet size. Not a big change but it will make life easier for some.
Other changes are pretty much just bug-fixes and cleanup of my development environment.
As always, download is available on these pages or from within application.