Author Topic: Waaayyyy off topic (sorry)  (Read 2204 times)

0 Members and 1 Guest are viewing this topic.

Offline Para-Noid

  • Avast Evangelist
  • Starting Graphoman
  • ***
  • Posts: 6700
  • Trust only what you test yourself!
Waaayyyy off topic (sorry)
« on: March 04, 2011, 06:18:44 AM »
Is there a simple and free way to fix an "error 1361"?
I wasn't kidding it's way off topic.
Dell Inspiron, Win10x64--HP Envy Win10x64--Both systems Avast Free v17.9.2322, Comodo Firewall v8.2 w/D+, MalwareBytes v3.0, OpenDNS, Super Anti-Spyware, Spyware Blaster, MCShield, Unchecky, Vivaldi Browser and, various browser security tools.

"Look before you leap!" Use online scanners before you click on any link.

Offline YLAP

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 2118
Re: Waaayyyy off topic (sorry)
« Reply #1 on: March 04, 2011, 06:23:02 AM »
Runtime Error 1361

1.Faulty Installations
If you suspect that the Runtime Error 1361 message is generated due to a faulty installation, simply reinstall the program. However, if your source for the program is damaged, then you need to obtain a fresh disk or download before attempting the installation. Once the program has been properly installed, the Runtime Error 1361 should no longer occur.

2.Virus Infection
When a virus infects your computer, a number of problems can arise including Runtime Error 1361. If the Runtime Error 1361 message is generated due to a virus infection, simply scan your computer with an up-to-date anti-virus program to remove it.

3.Incorrect Regional Settings
If the settings on your computer are incorrect, Runtime Error 1361 can occur. Make sure that the date settings on your computer match those for the country you are in.

4.Obsolete msvcrt.dll File
If the runtime error is due to an obsolete msvcrt.dll file, you need to replace the file by updating your operating system. You can do so by visiting the Microsoft website and check for any existing hot fixes which have been updated for your version of Windows.

5.Outdated MS DCOM File
If the runtime error is due to an outdated MS DCOM file, then obtain the latest updates for your operating system through Microsoft’s website.

6.Missing stdole32.tlb File
If you are missing the stdole32.tlb file, you need to download and replace it. While you might be able to obtain this file from several different websites, it is best to obtain it through the Microsoft dll library.

7.Broken or Missing Registry Files
Registry files that have become broken or damaged can be repaired by running a reputable registry cleaner on your computer. Several different ones are available. Select the one that you want, download it, install it, and run it to repair your Windows system.

Offline Para-Noid

  • Avast Evangelist
  • Starting Graphoman
  • ***
  • Posts: 6700
  • Trust only what you test yourself!
Re: Waaayyyy off topic (sorry)
« Reply #2 on: March 04, 2011, 06:29:08 AM »
Thanks, the updates might be in the optional list. Will download then report back...probably tomorrow.
Dell Inspiron, Win10x64--HP Envy Win10x64--Both systems Avast Free v17.9.2322, Comodo Firewall v8.2 w/D+, MalwareBytes v3.0, OpenDNS, Super Anti-Spyware, Spyware Blaster, MCShield, Unchecky, Vivaldi Browser and, various browser security tools.

"Look before you leap!" Use online scanners before you click on any link.