Windows command line window is resizable only vertically. If you want to resize it horizontally you have to change its settings, which takes time and is permanent.
A simple and quick trick will enable a command line window to be resized for one session:
wmicCtrl+CIf you don’t skip step 2 your window will stay resizable.
Took me a while to figure this one out.
The reason for the error was insufficient space in the Windows System Reserved partition. I had to shrink my C drive and expand the System Reserved partition. (I used GParted from Linux, you can use a boot CD like PartedMagic or whatever method works for you).
Windows boot might break because of this. You’ll get error 0xc0000225.
You’ll have to boot from a Windows 8(.1) installation media, get to the command line and then:
diskpartselect disk 0 (0 is the number of the drive)list partition to see make sure this is the right drive and to find the system reserved partition number.select partition 1 (change 1 to the reserved partition number)activeexit to close the toolbcdboot C:\Windows (change C to the partition where Windows in installed).Windows should boot now. You can use EasyBCD to remove the old unbootable BCD entry.
Hope it helps.
One day my Windows 8.1 stopped shutting down. Restart works but shutdown seems to just turn off the screen after writing “Shutting down”. Clicking the mouse wakes the computer up at once.
This bug seems to be a feature, weirdly, a counter useful one in my opinion. It makes sure that you can turn the computer back on quickly by not shutting down. I can see the use in tablets but this is a PC. Really stupid decision.
Anyway, you can turn it off.
In my opinion, turning this on by default on PC’s is a stupid decision.
If your computer doesn’t have an optical (DVD) drive, how do you install Windows?
It happened to me twice on a new installation of Windows XP. In the first time I reinstalled Windows to fix it. On the second time I researched a bit and found the problem to be the installation of .NET 4.
The only way I found to fix it was to uninstall .NET 4 completely. Repair of .NET 4 or of Windows update did not help.
As far as I know, if you use Windows XP you have to live without .NET 4 or without Windows Update. If you use newer versions of Windows you can try installing .NET 4.5 since it’s a replacement of .NET 4. Unfortunately Windows XP is not supported by .NET 4.5.
I would love to know if you have a solution for Windows XP users.
([url=https://social.technet.microsoft.com/Forums/en-US/itproxpsp/thread/fdd723f8-af81-4331-8c56-0b09432d92bc]a conversation about the topic[/url])
Update: I have asked the quesion on superuser.com and some time after trying to solve the problem it started working. I don’t know what helped or if it is something from this page but [url=http://superuser.com/questions/636554/how-to-install-net-4-on-windows-xp-without-getting-error-0x8024402f-from-window]you can try[/url].
I have two hard drives, one is SATA and the other one is an old IDE (PATA). I use mostly the IDE because it is larger.
The SATA was causing errors which crashed my Windows and Linux OS’s so I disconnected it altogether. The crashes vanished, but XP became inconceivably slow. Boot was taking about 30 seconds, it became a few minutes. Opening applications was also very slow.
I didn’t have a clue what could cause that so I searched, and after some time I have found this: [url=http://support.microsoft.com/default.aspx?scid=kb;en-us;817472]Link to Microsoft support[/url]
Basically what it says is that for some reason, after too many I/O errors, Windows XP changes the way it interacts with the hard drive to be very slow and reliable. When the I/O errors stop happening it should have been reverted to the fast method again but that does not happen.
To fix that, first eliminate the source of I/O errors (in my case, the SATA drive), and then uninstall the IDE controller driver through Device Manager. Reboot, and Windows will install the correct driver, reboot again and voila, your XP is fast again.