Technology Tales

Getting rid of Windows 10 notifications about disabling start-up applications

On several Windows 10 machines, I have been seeing messages appearing in its Action Centre pane with the heading Disable apps to help improve performance. It appeared again recently, so I decided to look further into the matter.

What I found was that the solution first involves opening up the Control Panel, which takes a little finding in Windows 10. You could use Cortana to get to it or right-clicking on the Start Menu and left-clicking on the Control Panel menu. Using the Windows key + X will produce the same menu, and choosing the same entry will have the same effect.

Once the Control Panel is open, it makes life a little easier if you change to the Large icons view using the drop-down menu under the Search Control Panel box on the right-hand side. Then, what you need to do is click on the Security and Maintenance icon.

Once in that Security and Maintenance section, you are presented with two subheadings, one for Security and one for Maintenance. So long as you have not dismissed the message in the action centre, you will see a corresponding entry under the Maintenance section. At the bottom of that entry, there will be a link that turns off these messages permanently, and clicking on this will have the desired effect.

Resolving Windows Update Error 0x80244019 on Windows 10

In Windows 10, the preferred place to look if you fancy prompting an update of the system is in the Update & Security section of the Settings application. At the top is the Windows Update, and the process usually is as simple as pressing the Check for updates button. For most of the time, that has been my experience, but it stopped working on my main Windows 10 virtual machine, so I needed to resolve the problem.

Initially, going into the Advanced Options section and deselecting the tick box for Give me updates for other Microsoft products when I update Windows helped. However, it seemed a non-ideal solution, so I looked further. When it was then that I found that manually resetting a system's Windows Updates components helped others, I tried that and restarted the system.

The first part of the process was to right-click on the Start Menu button and select the Windows PowerShell (Admin) entry from the menu that appeared. This may be replaced by Command Prompt (Admin) on your system on your machine, but the next steps in the process are the same. In fact, you could include any commands you see below in a script file and execute that if you prefer. Here, I will run through each group in succession.

From either PowerShell or the Command Prompt, you need to stop the Windows Update, Cryptographic, BITS (or Background Intelligent Transfer Service) and MSI Installer services. To accomplish this, execute the following commands at a command prompt:

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver

With the services stopped, it is then possible to rename the SoftwareDistribution and Catroot2 folders so you can refresh everything to remove them. To accomplish this, execute the following pair of commands using either PowerShell or the Command Prompt:

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 Catroot2.old

Once you have the folders renamed, then you can start the Windows Update, Cryptographic, BITS and MSI Installer services by executing the following commands in either PowerShell or the Command Prompt:

net start wuauserv
net start cryptSvc
net start bits
net start msiserver

Once these have completed, you may close the PowerShell or Command Prompt window that you were using and restart the machine. Going into the Update & Security section of the Settings tool afterwards and pressing the Check for updates button now builds new versions of the folders that you renamed, and this takes a little while longer than the usual update process. Otherwise, you could let your system rebuild things in its own time. As it happens, I opted for manual intervention and all has worked well since then.

Initial impressions of Windows 10

Being ever curious on the technology front, the release of the first build of a Technical Preview of Windows 10 was enough to get me having a look at what was on offer. The furore regarding Windows 8.x added to the interest, so I went to the download page to get a 64-bit installation ISO image.

That got installed into a fresh VirtualBox virtual machine and the process worked smoothly to give something not so far removed from Windows 8.1. However, it took until release 4.3.18 of VirtualBox before the Guest additions had caught up with the Windows prototype, so I signed up for the Windows Insider program and got a 64-bit ISO image to install the Enterprise preview of Windows 10 into a VMware virtual machine since and that supported full screen display of the preview while VirtualBox caught up with it.

Of course, the most obvious development was the return of the Start Menu, and it works exactly as expected too. Initially, the apparent lack of an easy way to disable App panels had me going to Classic Shell for an acceptable Start Menu. It was only later that it dawned on me that unpinning these panels would deliver to me the undistracting result that I wanted.

Another feature that attracted my interest is the new virtual desktop functionality. Here I was expecting something like what I have used on Linux and UNIX. There, each workspace is a distinct desktop, with only the applications open in a given workspace showing on a panel in there. Windows does not work that way with all applications visible on the taskbar regardless of what workspace they occupy, which causes clutter. Another deficiency is not having a desktop indicator on the taskbar instead of the Task View button. On Windows 7 and 8.x, I have been a user of VirtuaWin and this still works largely in the way that I expect of it too, except for any application windows that have some persistence associated with them; the Task Manager is an example and I include some security software in the same category too.

Even so, here are some keyboard shortcuts for anyone who wants to take advantage of the Windows 10 virtual desktop feature:

• Create a new desktop: Windows key + Ctrl + D
• Switch to previous desktop: Windows key + Ctrl + Left arrow
• Switch to next desktop: Windows key + Ctrl + Right arrow

Otherwise, stability is excellent for a preview of a version of Windows that is early on its road to final release. An upgrade to a whole new build went smoothly when initiated following a prompt from the operating system itself. All installed applications were retained, and a new taskbar button for notifications made its appearance alongside the existing Action Centre icon. So far, I am unsure what this does and whether the Action Centre button will be replaced in the fullness of time, yet I am happy to await where things go with this.

All is polished up to now, and there is nothing to suggest that Windows 10 will not be to 8.x what 7 was to Vista. The Start Screen has been dispatched after what has proved to be a misadventure for Microsoft. Regardless of what was hyped a few years ago, the PC still is with us; touchscreen devices like tablets are augmenting it instead of replacing it for any tasks involving some sort of creation. If anything, we have seen the PC evolve with laptops perhaps becoming more like the Surface Pro, at least when it comes to hybrid devices. However, we are not as happy to smudge our PC screens quite like those on phones and tablets, so a return to a more keyboard and mouse centred approach for some devices is welcome.

What I have here are just a few observations; there are more elsewhere, including a useful article by Ed Bott on ZDNet. All in all, we are early in the process for Windows 10 and, though it looks favourable so far, I will continue to keep an eye on how it progresses. The need to be less experimental than Windows 8.x is being fulfilled: so far, it certainly is less schizophrenic and should not be a major jump for users of Windows 7.

Adding a Start Menu to Windows 8

For all the world, it looks like Microsoft has mined a concept from a not often recalled series of Windows: 3.x. Then, we had a Program Manager for starting all our applications, with no sign of a Start Menu. That came with Windows 95 and I cannot see anyone mourning the burying of the Program Manager interface either. It was there in Windows 95 if you knew where to look, and I do remember starting an instance, possibly out of curiosity.

Every Windows user seems to have taken to the Start Menu, regardless of how big it can grow when you install a lot of software on your machine. It didn't matter that Windows NT got it later than Windows 9x ones either; NT 3.51 has the Program Manager too, and it was NT 4 that got the then new interface that has been developed and progressed in no less than four subsequent versions of Windows (2000, XP, Vista & 7). Maybe it was because computing was the preserve of fewer folk that the interchange brought little if any sign of a backlash. The zeitgeist of the age reflected the newness of desktop computing, and its freshness probably brought an extra level of openness too.

Things are different now, though. You only have to hear of the complaints about changes to Linux desktop environments to realise how attached folk become to certain computer interfaces. Ironically, personal computing has just got exciting again after a fairly stale decade of stasis. Mobile computing devices are aplenty nowadays, and it no longer is a matter of using a stationary desktop PC or laptop, even if those brought their own excitement in the 1990's. In fact, reading a title like Computer Shopper reminds me of how things once were with it's still sticking with PC reviews while others are not concentrating on them as much. Of course, the other gadgets get reviewed too, so it is not stuck in any rut. Still, it is good to see the desktop PC getting a look in an age when there is so much competition, especially from phones and tablets.

In this maelstrom, Microsoft has decided to do something dramatic with Windows 8. It has resurrected the Program Manager paradigm in the form of the Start screen and excised the Start Menu from the desktop altogether. For touch screen computing interfaces such as tablets, you can see the sense of this, but it's going to come as a major surprise to many. Removing what lies behind how many people interact with a PC is risky, so you have to wonder how it will work out for all concerned.

What reminded me of this was a piece on CNET by Mary Jo Foley. Interestingly, software is turning up that returns the Start Menu to Windows 8. One of these is Classic Shell, and I decided to give it a go on a Windows 8 Enterprise evaluation instance that I have. Installation is like any Windows program, and I limited the options to the menu and updater. At the end of the operation, a button with a shell icon appeared on the desktop's taskbar. You can make the resultant menu appear like that of Windows XP or Windows 7 if you like. There are other settings like what the Windows key does and what happens when you click on the button with a mouse. By default, both open the new Start Menu, and holding down the Shift key when doing either brings up the Start screen. This is customisable, so you can have things the other way around if you so desire. Another setting is to switch from the Start screen to the desktop after you log into Windows 8 (you may also have it log in for you automatically, but it's something that I do not think anyone should be doing). While the Start screen does flash up, things move along quickly; maybe having not appear at all would be better for many.

Classic Shell is free of charge and worked well for me, apart from that small rough edge noted above. It is also open source and looks well maintained too. For that reason, it appeals to me more than Stardock's Start8 (currently in beta release at the time of writing) or Pokki for Windows 8, which really is an App Store that adds a Start Menu. If you encounter Windows 8 on a new computer, then they might be worth trying should you want a Start Menu back. Being an open-minded type, I could get along with the standard Windows 8 interface, yet it's always good to have choices too. Most of us want to own our computing experience, it seems, so these tools could have their uses for Windows 8 users.

Restoring the MBR for Windows 7

During my explorations of dual-booting of Windows 7 and Ubuntu 10.10, I ended up restoring the master boot record (MBR) so that Windows 7 could load again or to find out if it wouldn't start for me. The first hint that came to me when I went searching was the bootsect command, but this only updates the master boot code on the partition, so it did nothing for me. What got things going again was the bootrec command.

To use either of these, I needed to boot from a Windows 7 installation DVD. With my Toshiba Equium laptop, I needed to hold down the F12 key until I was presented with a menu that allowed me to choose from what drive I wanted to boot the machine, the DVD drive in this case. Then, the disk started and gave me a screen where I selected my location and moved to the next one where I selected the Repair option. After that, I got a screen where my Windows 7 installation was located. Once that was selected, I moved on to another screen from I started a command line session. Then, I could issue the commands that I needed.

bootsect /nt60 C:

This would repair the boot sector on the C: drive in a way that is compatible with BOOTMGR. Though this wasn't enough for me, it was something worth trying anyway in case there was some corruption.

bootrec /fixmbr
bootrec /fixboot

The first of these restores the MBR, and the second sorts out the boot sector on the system drive (where the Windows directory resides on your system). In the event, I ran both of these and Windows restarted again, proving that it had come through disk partition changes without a glitch, though CHKDISK did run in the process, but that's understandable. There's another option for those wanting to get back their boot menu, and here it is:

bootrec /rebuildbcd

Though I didn't need to do so, I ran that too, but later used EasyBCD to remove the boot menu from the start-up process because it was surplus to my requirements. That's a graphical tool that has gained something of a reputation since Microsoft dispensed with the boot.ini file that came with Windows XP for later versions of the operating system.

Consolidation

For a while, the Windows computing side of my life has been spread across far too many versions of the pervasive operating systems with the list including 2000 (desktop and server), XP, 2003 Server, Vista and 7; 9x hasn't been part of my life for what feels like an age. At home, XP has been the mainstay for my Windows computing needs, with Vista Home Premium loaded on my Toshiba laptop. The latter variant came in for more use during that period of home computing "homelessness" and, despite a cacophony of complaints from some, it seemed to work well enough. Since the start of the year, 7 has also been in my sights with beta and release candidate instances in virtual machines, leaving me impressed enough to go popping the final version onto both the laptop and in a VM on my main PC. Microsoft finally has got around to checking product keys over the net, so that meant a licence purchase for each installation using the same downloaded 32-bit ISO image. 7 is still doing well for me, so I am beginning to wonder whether having an XP VM is becoming pointless. The reason for that train of thought is that 7 is becoming the only version that I really need for anything that takes me into the world of Windows.

Work is a different matter, with a recent move away from Windows 2000 to Vista heavily reducing my exposure to the venerable old stager (businesses usually take longer to migrate, and any good IT manager usually delays any migration by a year anyway). 2000 is sufficiently outmoded by now that even my brother was considering a move to 7 for his work because of all the Office 2007 files that have been coming his way. While he may be no technical user, the bad press gained by Vista hasn't passed him by, so a certain wariness is understandable. Saying that, my experiences with Vista haven't been unpleasant, and it always worked well on the laptop, while the same also can be said for its corporate desktop counterpart. Much of the noise centred around issues of hardware and software compatibility, and that certainly is apparent at work with my having some creases left to straighten.

With all of this general forward heaving, you might think that IE6 would be shuffling its mortal coil by now, but a recent check on visitor statistics for this website places it at about 13% share, tantalisingly close to oblivion but still too large to ignore it completely. All in all, it is lingering like that earlier blight of web design, Netscape 4.x. If I was planning a big change to the site design, setting up a Win2K VM would be in order, not to completely put off those labouring with the old curmudgeon. For smaller changes, the temptation is not to bother checking, but that is questionable when XP is set to live on for a while yet. That came with IE6 and there must be users labouring with the old curmudgeon, and that's ironic with IE8 being available for SP2 since its original launch a while back. Where all this is leading me is towards the idea of waiting for IE6 share to decrease further before tackling any major site changes. After all, I can wait with the general downward trend in market share; there has to be a point when its awkwardness makes it no longer viable to support the thing. That would be a happy day.

Never undercutting the reseller...

Quite possibly, THE big technology news of the week has been the launch of Windows 7. Regular readers may be aware that I have been having a play with the beta and release candidate versions of the thing since the start of the year. In summary, I have found to work both well and unobtrusively. While there have been some rough edges when accessing files through VirtualBox's means of accessing the host file system from a VM, that's the only perturbation to be reported and, even then, it only seemed to affect my use of Photoshop Elements.

Therefore, I had it in mind to get my hands on a copy of the final release after it came out. Of course, there was the option of pre-ordering, but that isn't for everyone, so there are others. A trip down to the local branch of PC World will allow you to satisfy your needs with different editions: full, upgrade (if you already have a copy of XP or Vista, it might be worth trying out the Windows Secrets double installation trick to get it loaded on a clean system) and family packs. The last of these is very tempting: three Home Premium licences for around £130. Though wandering around to your local PC components emporium is an alternative, you have to remember that OEM versions of the operating system are locked to the first (self-built) system on which they are installed. Apart from that restriction, the good value compared with retail editions makes them worth considering. The last option that I wish to bring to your attention is buying directly from Microsoft themselves. You would think that this may be cheaper than going to a reseller, but that's not the case with the Family Pack costing around £150 in comparison to PC World's pricing, and it doesn't end there. That they only accept Maestro debit cards along with credit cards from the likes of Visa and Mastercard perhaps is another sign that Microsoft is new to the whole idea of selling online. In contrast, Tesco is no stranger to online selling, yet they also have Windows 7 on offer though they aren't noted for computer sales; PC World may be forgiven for wondering what that means, but who would buy an operating system along with their groceries? I suppose that the answer to that would be that people who are accustomed to delivering one's essentials at a convenient time should be able to do the same with computer goods too. That convenience of timing is another feature of downloading an OS from the web, and many a Linux fan should know what that means. While Microsoft may have discovered this of late, that's better than never.

Because of my positive experience with the pre-release variants of Windows 7, I am very tempted to get my hands on the commercial release. Because I have until early next year with the release candidate and XP works sufficiently well (it ultimately has given Vista something of a soaking), I'll be able to bide my time. When I do make the jump, it'll probably be Home Premium that I'll choose because it seems difficult to justify the extra cost of Professional. It was different in the days of XP, when its Professional edition did have something to offer technically minded home users like me. With 7, XP Mode might be a draw, but with virtualisation packages like VirtualBox available for no cost, it's difficult to justify spending extra. In any case, I have Vista Home Premium loaded on my Toshiba laptop and that seems to work fine, despite all the bad press that Vista has got itself.

Running Windows 7 within VirtualBox

With all the fanfare that surrounded the public beta release of Windows 7, I suppose that the opportunity to give it a whirl was too good to miss. Admittedly, Microsoft bodged the roll-out by underestimating the level of interest and corralling everyone into a 24-hour time slot, with one exacerbating the other. In the event, they did eventually get their act together and even removed the 2.5 million licence limit. Thus, I suppose that they really needed to get 7 right after the unloved offering that was Vista, so they probably worked out that the more testers that they get, the better. After, it might be observed that the cynical view that the era of making people pay to "test" your products might be behind us and that users just want things to work well if not entirely faultlessly these days.

After several abortive raids, I eventually managed to snag myself a licence and started downloading the behemoth using the supplied download manager. I foresaw it taking a long time and so stuck with the 32-bit variant so as not to leave open the possibility of that part of the process using up any more of my time. As it happened, the download did take quite a few hours to complete, but this part of the process was without any incident or fuss.

Once the DVD image was downloaded, it was onto the familiar process of building myself a VirtualBox VM as a sandbox to explore the forthcoming incarnation of Windows. After setting up the ISO file as a virtual DVD, installation itself was an uneventful process, yet subsequent activities weren't without their blemishes. The biggest hurdle to be overcome was to get the virtual network adapter set up and recognised by Windows 7. The trick is to update the driver using the VirtualBox virtual CD as the source because Windows 7 will not recognise it using its own driver repository. Installing the other VirtualBox tools is a matter of going to Compatibility page in the Properties for the relevant executable, the one with x86 in the file name in my case, and setting XP as the Windows version (though Vista apparently works just as well, I played safe and depended on my own experience). While I was at it, I allowed the file to run under the administrator account, too. Right-clicking on executable files will bring you to the compatibility troubleshooter that achieves much the same ends but by a different route. With the Tools installed, all was workable rather than completely satisfactory. Shared folders have not worked for, but that might need a new version of the VirtualBox software or getting to know any changes to networking that come with Windows 7. I plan to stick with using USB drives for file transfer for the moment. Though stretching the screen to fit the VirtualBox window was another thing that would not happen, that's a much more minor irritation.

With those matters out of the way, I added security software from the list offered by Windows with AVG, Norton and Kaspersky being the options on offer. I initially chose the last of these but changed my mind after seeing the screen becoming so corrupted as to make it unusable. That set me to rebuilding the VM and choosing Norton 360 after the second Windows installation had finished. That is working much better, and I plan to continue my tinkering beyond this. I have noticed the inclusion of PowerShell and an IDE for the same, so that could be something that beckons. All in all, there is a certain solidity about Windows 7, though I am not so convinced of the claim of speedy startups at this stage. Time will tell and, being a beta release, it's bound to be full of debugging code that will not make it into the final version that is unleashed on the wider public.

System error codes for Windows

Windows system error codes can be indecipherable, so it's useful to have a list. Microsoft has one on its Microsoft Learn website that may help. However, the decodes may not as explicit as I would like, but they're better than nothing when you don't get anything other than the number.

A year in the making…

It was a year ago that I set this blog on the go. Then, I was exploring the possibilities offered by WordPress.com. After some months, I decided that I wanted to make my own decisions rather than have them, so I went independent in June. Between those dates, some big launches took my attention: Windows Vista, Office 2007 & CS3 come to mind. All the while, my experience of UNIX, Oracle and other such matters kept growing more and more. In the latter half of the year, I finally made the leap from Windows to Linux on the home computing front, a decision that taught me a lot and one that I don't regret. Other subjects featured from time to time as well; my musings on web development and blogging made their appearance too. 2007 was a packed year on the technology front, and 2008 is only just getting under way. There's a Vista laptop, and I am already picking up ideas for posts, though I am not going to force them out like I might have tried to do last year. 2008 may be a spot more leisurely, but I hope that it's just as interesting.