Session 0 identifies the locally logged in user on Windows operating system. Since I intend to write this blog on Windows and software development issues, I felt that this was an apt title.
I also chose the title Session 0 because it relates to one of the main topics that I intend to blog on: Windows Vista. In Windows Vista Microsoft has introduced Session 0 isolation which changes the Windows kernel so that no user logs on as Session 0, to enhance system stability.
So, that’s the name.
Yeee-haw. First poster ever! Looking forward to reading more.
Hi,
We have a Windows Service which runs office automation using MS Office COM objects. It used to work fine with Win XP and Vista Beta1, but it no longer works with Vista RC1.
When we call IDispatch->Invoke “Open” of the Word Application Object, we get an error (”Open”) failed with error 0×800a13e9.
Could you please help
Thanks and regards,
Mridu
Hey Mridu,
This type of service, that is trying to create UI and interact with the loged on session will no longer work in the same way with Vista. Since users in Windows Vista are no longer logged into Session 0, the service can no longer interact directly with the user.
One of the ways that you can change your code to work in Windows Vista is to use the CreateProcessAsUser function to create a process in the user’s session.
You can read more about this here:
Impact of Session 0 Isolation on Services and Drivers in Windows Vista