Ever needed to make a PC Shutdown, Reboot, Hibernate, … after running some code?
As with most things, there are a number of possible approaches, but today I thought I’d demonstrate a very simple solution using the Shutdown command:
Ever needed to make a PC Shutdown, Reboot, Hibernate, … after running some code?
As with most things, there are a number of possible approaches, but today I thought I’d demonstrate a very simple solution using the Shutdown command:
As an FYI for those of you curious, I’ve been trying to ascertain the true impact of the VBScript deprecation.
Sadly, the official announcement provides 0 details whatsoever as to the impacted libraries/components. Feel free to check for yourself by using the 2 links provided below:

If you’ve been following my blog in recent months you are aware that Microsoft is now blocking macros downloaded from external sources (e-mails, internet, …). If you aren’t aware then I urge you to review:

Now, I wrote about unblocking the macro so you could use the files again, refer to:
but recently a fellow MVP brought up a weird error when they tried to unblock a file and I thought I’d post the information here for all to benefit from.
If ever you are trying to reverse engineer the full path of a mapped drive, nothing could be easier (once you know how!).


It will then give you a breakdown of all the mapped drive with their full paths.
Last week I was working on a clients PC and this is what happened when I rebooted the computer (in this instance Windows 7).
I believe this image speaks louder than any words ever could.
How can any company, little alone one like Microsoft, be releasing software that requires 135 updates? Definitely something seriously wrong with this picture.
Some will argue this demonstrates Microsoft’s commitment to improving the user experience. I put forth that this clearly illustrates their commitment to profit by releasing software that clearly is not ready for the mass market.
I’d also like to know how Microsoft expects users without high-speed internet connection to be able to download and install these updates. This is simply unrealistic! This puts them at even greater risk of being hacked, infected by viruses, malware, … and simply being exploited.
You be the judge!
PS: Another reboot installed even more updates?!
I was recently migrating a client from an older laptop with Office 2007 to a new laptop with Office 2010 and wanted to even transfer their Quick Access Toolbars (QAT).
Exporting your Quick Access Toolbar from MS Office 2007
So the first issue was determining where MS Office stores such information. In realitym this is very straight forward. In MS Office 2007, each application create one or many *.QAT files to store any customization made to the quick access toolbar by the user and these files can be located in:
For Windows XP:
C:\Documents and Settings\%username%\Local Settings\Application Data\Microsoft\Office
%systemdrive%\Documents and Settings\%username%\Local Settings\Application Data\Microsoft\Office
%AppData%\Microsoft\Office
For Windows Vista and Windows 7
C:\Users\%username%\AppData\Local\Microsoft\Office
%systemdrive%\Users\%username%\AppData\Local\Microsoft\Office
Then simply copy and *.QAT files so you can migrate them to your MS Office 2010 installation.
Importing your Quick Access Toolbar into MS Office 2010
The process is once again very simple:
The critical step is renaming the files properly!
That’s it, that’s all!