Ms FronPage Sandbox Problems

I recently installed MS Office XP Pro. When FrontPage is launched, it is sandboxed and the Windows Installer runs. If I try to add frontpg.exe to My Own Safe Files, CIS tells me that it is already a safe file and won’t let me add it. I have to add it through the sandbox pop-up. After it is added to My Own Safe Files, FrontPage launched as expected. The Windows Installer didn’t run.

I submitted frontpg.exe through the Web Submit Page. I just got an email back stating that they couldn’t find a problem and to submit the problem here if it still existed after updating to the most recent database. Let me know if you need any additional information.

Win XP Pro SP3
FrontPage v10.2623.2625
AMD Athlon 1600
1 GB Ram
120 GB HDD

OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 3 Build 2600
OS Manufacturer Microsoft Corporation
System Type X86-based PC
Processor x86 Family 6 Model 6 Stepping 2 AuthenticAMD ~1400 Mhz
BIOS Version/Date Award Software, Inc. ASUS A7V333 ACPI BIOS Revision 1012, 8/23/2002
SMBIOS Version 2.3
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = “5.1.2600.5512 (xpsp.080413-2111)”
Time Zone Eastern Daylight Time
Total Physical Memory 1,024.00 MB
Available Physical Memory 471.72 MB
Total Virtual Memory 2.00 GB
Available Virtual Memory 1.96 GB
Page File Space 2.41 GB
Page File D:\pagefile.sys

The frontpg.exe file can be downloaded here.

Please, check the box ‘Do not run this application inside the Sandbox again’!


I know I can do that! I don’t want to have to add a vast amount of my programs to that list. I have many programs that are Sandboxed and they work fine. The problem is, it should be on the safe list! I found the answer though, just disable the Sandbox! ;D For me, it has been nothing but a pain since its inception. >:( I’m going to leave it disabled until the next version release. I’ll give it another shot in version 5.0.

This MS FrontPage problem has now been resolved. The Devs were able to track the problem down and the fix is included in the 5481 DB update. Hats off to the Comodo Group! :wink: