Windows-based task schedule unconventional self-starting method, device and related media

Abstract

This invention discloses a method, apparatus, and related medium for unconventional auto-start of Windows Task Scheduler. The method includes: locating and extracting the system task scheduler; constructing a DLL module and system task scheduler parameters; registering the DLL module as a COM component and generating a class identifier; adding the system task scheduler parameters to the system task scheduler and binding the class identifier to the system task scheduler; setting the highest privileges and utilizing these privileges to achieve unconventional auto-start of the system task scheduler. This invention, by constructing the DLL module and the system task scheduler parameters and utilizing the highest privileges to achieve unconventional auto-start of the system task scheduler, avoids the program being mistakenly deleted by antivirus software. Furthermore, after the program starts automatically, the highest privileges allow the program process to remain running in the background.

Description

Technical Field

[0001] This invention relates to the field of program auto-start technology, and in particular to unconventional auto-start methods, devices and related media for Windows-based Task Scheduler. Background Technology

[0002] Currently, many programs in Windows systems need to start automatically at boot and remain resident in the system background to ensure they are always running. However, existing technologies for program startup in Windows have limitations. There are currently five main methods for Windows programs to start automatically: startup directory, registry startup items, system configuration files, Task Scheduler, and Windows service startup. These five startup methods are prime targets for antivirus software, making them prone to false positives or false negatives, which can prevent programs from starting and disrupt their normal operation.

[0003] When a program is falsely flagged or falsely flagged, the developer needs to contact the antivirus software to request that their program be added to the antivirus software's whitelist. This application process takes at least 1 to 3 business days, which increases the time cost for the software development company. Summary of the Invention

[0004] This invention provides a method, apparatus, and related media for unconventional automatic startup of Windows-based task scheduling, aiming to solve the problem that conventional software startup methods in Windows systems are easily mistakenly deleted by antivirus software.

[0005] In a first aspect, embodiments of the present invention provide a method for unconventional auto-start of Windows Task Scheduler, comprising:

[0006] Locate the system task plan and extract the system task plan to obtain system task plan data; wherein, the system task plan data includes a system task plan directory;

[0007] Based on the system task plan data, construct the DLL module and system task plan parameters respectively; and register the DLL module as a COM component and generate a class identifier;

[0008] Check if the system task schedule directory exists; if it does not exist, create a new system task schedule directory and reset the trigger; if it exists, do not reset the trigger; wherein, the trigger is used to set the attributes of the system task schedule.

[0009] Add the system task plan parameters to the system task plan, and bind the class identifier to the system task plan;

[0010] Save the system task schedule to the system task schedule directory, set the highest privileges, and use the highest privileges to enable the unconventional auto-start of the system task schedule.

[0011] Secondly, embodiments of the present invention provide a Windows-based unconventional auto-start device for task scheduling, comprising:

[0012] The task plan acquisition unit is used to locate system task plans and extract the system task plans to obtain system task plan data; wherein, the system task plan data includes a system task plan directory;

[0013] The task plan construction unit is used to construct a DLL module and system task plan parameters according to the system task plan data; and to register the DLL module as a COM component and generate a class identifier.

[0014] A task schedule detection unit is used to detect whether the system task schedule directory exists; if it does not exist, a new system task schedule directory is created and the trigger is reset; if it exists, the trigger is not reset; wherein, the trigger is used to set the attributes of the system task schedule.

[0015] A task plan binding unit is used to add the system task plan parameters to the system task plan and bind the class identifier to the system task plan;

[0016] The task schedule startup unit is used to save the system task schedule to the system task schedule directory, set the highest privileges, and use the highest privileges to realize the unconventional self-start of the system task schedule.

[0017] Thirdly, embodiments of the present invention provide a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the Windows-based unconventional self-starting method of the first aspect.

[0018] Fourthly, embodiments of the present invention provide a computer-readable storage medium, wherein a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, it implements the Windows-based unconventional self-starting method of the first aspect.

[0019] This invention provides a method for unconventional auto-start of Windows Task Scheduler. The method includes: locating and extracting the system task scheduler; constructing a DLL module and system task scheduler parameters; registering the DLL module as a COM component and generating a class identifier; adding the system task scheduler parameters to the system task scheduler and binding the class identifier to the system task scheduler; setting the highest privileges and using these privileges to achieve unconventional auto-start of the system task scheduler. This invention, by constructing the DLL module and the system task scheduler parameters and using the highest privileges to achieve unconventional auto-start of the system task scheduler, avoids the program being mistakenly deleted by antivirus software. Furthermore, after the program starts automatically, the highest privileges allow the program process to remain running in the background.

[0020] This invention also provides a Windows-based unconventional self-starting device for task scheduling, a computer device, and a storage medium, which also have the aforementioned beneficial effects. Attached Figure Description

[0021] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0022] Figure 1 A flowchart illustrating a non-conventional auto-start method for Windows-based task scheduling provided in an embodiment of the present invention;

[0023] Figure 2 This invention provides another flowchart illustrating a Windows-based unconventional auto-start method for task scheduling.

[0024] Figure 3 This is a schematic block diagram of a Windows-based unconventional self-starting device for task scheduling, provided as an embodiment of the present invention. Detailed Implementation

[0025] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0026] It should be understood that, when used in this specification and the appended claims, the terms "comprising" and "including" indicate the presence of the described features, integrals, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or collections thereof.

[0027] It should also be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the invention. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.

[0028] It should also be further understood that the term "and / or" as used in this specification and the appended claims refers to any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0029] Please see below. Figure 1 , Figure 1 The flowchart of a non-conventional auto-start method for Windows task scheduling provided in this embodiment of the invention specifically includes steps S101 to S105.

[0030] S101. Locate the system task plan and extract the system task plan to obtain system task plan data; wherein, the system task plan data includes a system task plan directory;

[0031] S102. Based on the system task plan data, construct the DLL module and system task plan parameters respectively; and register the DLL module as a COM component and generate a class identifier;

[0032] S103. Check if the system task schedule directory exists; if it does not exist, create a new system task schedule directory and reset the trigger; if it exists, do not reset the trigger; wherein, the trigger is used to set the attributes of the system task schedule.

[0033] S104. Add the system task plan parameters to the system task plan, and bind the class identifier to the system task plan;

[0034] S105. Save the system task plan to the system task plan directory, set the highest privileges, and use the highest privileges to realize the unconventional self-start of the system task plan.

[0035] Combination Figure 2 As shown, Figure 2This is another flowchart illustrating how to use system task schedulers (such as "RegIdleBackup" under the "Microsoft\\Windows\\Registry" directory, which is a system task scheduler for idle registry backups) to achieve program auto-start and process resident in the background.

[0036] In step S101, the system task schedulers under the corresponding system directory "Microsoft\\Windows" are first traversed and searched. The system task scheduler to be operated on is selected (generally, a system task scheduler that is frequently triggered is selected to prevent the system task scheduler from failing to start in a timely manner for a long time, such as "RegIdleBackup" under the "Microsoft\\Windows\\Registry" directory). After selection, the system task scheduler is extracted to obtain the system task scheduler data. The system task scheduler data includes the system task scheduler directory (generally under the "Microsoft\\Windows" directory).

[0037] In one embodiment, the system task plan data further includes: system task plan name, trigger start frequency, operation attributes, and condition attributes.

[0038] In this embodiment, the trigger start frequency can be understood as the trigger start interval, the operation attribute is the operation step setting in the system task plan, and the condition attribute is the setting in the system task plan to trigger the next step when a certain condition is met; the system task plan is extracted to obtain the system task plan data, and saved to prepare for subsequent steps.

[0039] In step S102, after obtaining the system task plan data, a DLL module supporting COM components and the system task plan parameters are constructed according to the system task plan data. After the construction is completed, the DLL module is registered as a COM component and a class identifier (i.e., CLSID, the same below) is generated.

[0040] Specifically, the class identifier, also known as CLASSID or CLSID, is a unique identifier (UUID) associated with a class object. A class object that is ready to create multiple objects should register its CLSID in the task table of the system registry database so that the system can locate and load the executable code associated with that object.

[0041] In one embodiment, step S102 includes:

[0042] Export the functions DllGetClassObject, DllCanUnloadNow, DllRegisterServer, and DllUnregisterServer respectively; construct the directory location and name of the system task schedule respectively; construct the full path where the DLL module is stored.

[0043] In this embodiment, the DllGetClassObject function primarily retrieves class objects from the DLL module handler or from the object application. The DllGetClassObject function is used to obtain a class factory pointer, and the DLL module supporting COM components must implement the DllGetClassObject function within its application. Custom logic can be implemented within the DllGetClassObject function; for example, by not exiting the DllGetClassObject function, the dllhost.exe process that loads the module can remain running in the background.

[0044] The DllCanUnloadNow function is called when the system is idle to determine whether the COM component can be exited. The return value of the DllCanUnloadNow function can be customized to control the exit of the COM component.

[0045] The DllRegisterServer function registers the DLL module as a response function for the COM component. Generally, the added registry will respond to the "Regsvr32" command.

[0046] The DllUnregisterServer function is a response function for uninstalling COM components. It can delete the registration information of COM components in the registry and respond to the "Regsvr32 / u" command to uninstall COM components.

[0047] Additionally, the directory location for constructing the system task schedule can be represented as "Microsoft\\Windows\\***", for example, the "Microsoft\\Windows\\Registry" directory; the name of the system task schedule can be constructed, such as "RegIdleBackup"; finally, the full path of the DLL module in the system can be constructed for easy retrieval.

[0048] In one embodiment, step S102 further includes:

[0049] Register the DLL module as the COM component using the Regsvr32 command based on the full path; obtain the generated class identifier based on the COM component.

[0050] In this embodiment, the "Regsvr32" command and the full path of the DLL are used to register the DLL module as a COM component in the system, obtain the corresponding class identifier, and finally save the class identifier in the system. Specifically, the Regsvr32 command is used to register COM components. It is a command provided by the Windows system to register or unregister controls, and it is run in command-line mode. In Windows XP and later systems, regsvr32.exe is located in the Windows\system32 folder; in Windows 2000 systems, regsvr32.exe is located in the winnt\system32 folder.

[0051] In step S103, it is checked whether the system task scheduler directory exists; if the "Microsoft\\Windows\\***" directory does not exist (e.g., the "Microsoft\\Windows\\Registry" directory), a new system task scheduler directory is created and the trigger is reset; if the system task scheduler directory exists, the trigger is not reset; wherein, the trigger is used to set the attributes of the system task scheduler.

[0052] In one embodiment, step S103 includes:

[0053] Set the startup, creation, or modification time, recurring task interval, delayed task time, and duration for the new system task schedule directory.

[0054] In this embodiment, the corresponding attributes can be set according to the actual situation. The startup time, recurring task interval, delayed task time and duration of the new system task schedule directory can be set; the creation time, recurring task interval, delayed task time and duration of the new system task schedule directory can be set; and the modification time, recurring task interval, delayed task time and duration of the new system task schedule directory can also be set.

[0055] In step S104, after binding the class identifier to the system task plan, it is also added to the system task plan along with the system task plan parameters. Only after the class identifier is successfully bound can the next operation be performed, that is, to achieve the process to run in the background.

[0056] In one embodiment, step S104 includes:

[0057] Call the `get_Actions` function in the `ITaskDefinition` structure to obtain the `IActionCollection` structure; call the `get_Count` function in the `IActionCollection` structure to obtain the number of activities in the system task plan; traverse the `IAction` structures in the `IActionCollection` structure according to the number of activities in the system task plan, and call the `get_Item` function in the `IActionCollection` structure to obtain the `IAction` structure; determine whether the `IAction` structure contains the class identifier; if it does not exist, bind the class identifier to the system task plan; if it exists, return success directly.

[0058] Furthermore, the IComHandlerAction structure is obtained through the QueryInterface function in the IAction structure; the Create function in the IActionCollection structure is called to specify the IAction structure and create a new IAction structure; the QueryInterface function in the new IAction structure is called to bind the IComHandlerAction structure; and the put_ClassId function in the IComHandlerAction structure is called to specify the class identifier.

[0059] In this embodiment, firstly, the `get_Actions` function in the `ITaskDefinition` structure is called to obtain the `IActionCollection` structure, which represents the collection of all actions in the current system task plan (i.e., the number of activities, hereinafter the same). Then, the `get_Count` function in the `IActionCollection` structure is called to obtain the collection of actions in the current system task plan. Next, the `IAction` structures within the `IActionCollection` structure are traversed according to the number of activities in the system task plan, and the `get_Item` function in the `IActionCollection` structure is called to obtain the `IAction` structure. There can be multiple `IAction` structures, depending on the actual usage, and this is not limited here. Finally, it is determined whether the `IAction` structure contains the class identifier; if it does not, the class identifier is bound to the system task plan; if it does, success is returned directly.

[0060] Furthermore, firstly, the IComHandlerAction structure, i.e., the operation response structure of the IAction structure, is obtained through the QueryInterface function in the IAction structure; then, the Create function in the IActionCollection structure is called to specify the IAction structure to be executed to create a new IAction structure; the QueryInterface function in the new IAction structure is called to bind the IComHandlerAction structure; finally, the put_ClassId function in the IComHandlerAction structure is called to specify the class identifier generated when the DLL module is registered and the COM component is generated, thus completing the binding.

[0061] In step S105, the system task plan is saved to the system task plan directory and given the highest permission (i.e., "SYSTEM" permission, the same below). It is saved by the RegisterTaskDefinition method under ITaskFolder, and the TASK_CREATE_OR_UPDATE type and the "SYSTEM" permission are specified.

[0062] Additionally, when the system task scheduler starts, the system will create a dllhost.exe process with "SYSTEM" privileges, and call the DllGetClassObject function in the DLL module to be executed. The DllGetClassObject function allows users to define the code and logic that the program needs to execute. By not returning or exiting within the DllGetClassObject function, the dllhost.exe process with "SYSTEM" privileges can be kept running in the background.

[0063] In summary, the modified system task scheduler loads the custom DLL module and calls its functions upon startup, and possesses the "SYSTEM" privileges of the Windows system. These "SYSTEM" privileges enable tasks that are impossible with ordinary privileges and, due to the reliance on the system task scheduler, offer good stability. Furthermore, the startup method differs from conventional auto-start methods, effectively reducing false positives or deletions by antivirus software. If the program process is not exited while functions in the DLL module are being called, it can remain running in the background, making it applicable in most scenarios. Additionally, the system task scheduler can be configured to restart after failure and via scheduled restarts, and it includes Windows' built-in fault tolerance mechanisms.

[0064] Combination Figure 3As shown, Figure 3 A schematic block diagram of a Windows-based unconventional task scheduling auto-start device 300 provided in this embodiment of the invention includes:

[0065] The task plan acquisition unit 301 is used to search for system task plans and extract the system task plans to obtain system task plan data; wherein, the system task plan data includes a system task plan directory;

[0066] The task plan construction unit 302 is used to construct a DLL module and system task plan parameters according to the system task plan data; and to register the DLL module as a COM component and generate a class identifier;

[0067] The task plan detection unit 303 is used to detect whether the system task plan directory exists; if it does not exist, a new system task plan directory is created and the trigger is reset; if it exists, the trigger is not reset; wherein, the trigger is used to set the attributes of the system task plan;

[0068] The task plan binding unit 304 is used to add the system task plan parameters to the system task plan and bind the class identifier to the system task plan;

[0069] The task schedule startup unit 305 is used to save the system task schedule to the system task schedule directory, set the highest privileges, and use the highest privileges to realize the unconventional self-start of the system task schedule.

[0070] In this embodiment, firstly, the task plan acquisition unit 301 searches for the system task plan and extracts it to obtain system task plan data; wherein, the system task plan data includes the system task plan directory; the task plan construction unit 302 constructs DLL modules and system task plan parameters according to the system task plan data; and registers the DLL modules as COM components and generates class identifiers; then, the task plan detection unit 303 checks whether the system task plan directory exists; if it does not exist, a new system task plan directory is created and the trigger is reset; if it exists, the trigger is not reset; wherein, the trigger is used to set the attributes of the system task plan; the task plan binding unit 304 adds the system task plan parameters to the system task plan and binds the class identifier to the system task plan; finally, the task plan startup unit 305 saves the system task plan to the system task plan directory, sets the highest privileges, and uses the highest privileges to realize the unconventional self-starting of the system task plan.

[0071] In one embodiment, the system task plan data further includes: system task plan name, trigger start frequency, operation attributes, and condition attributes.

[0072] In one embodiment, the task planning construction unit includes:

[0073] The export unit is used to export the functions DllGetClassObject, DllCanUnloadNow, DllRegisterServer, and DllUnregisterServer, respectively.

[0074] The construction unit is used to construct the directory location and the name of the system task plan, respectively.

[0075] The path unit is used to construct the full path where the DLL module is stored.

[0076] In one embodiment, the task planning construction unit further includes:

[0077] The registration unit is used to register the DLL module as the COM component using the Regsvr32 command based on the full path;

[0078] The generation unit is used to obtain the generated class identifier based on the COM component.

[0079] In one embodiment, the task planning detection unit includes:

[0080] The setting unit is used to set the start time, creation or modification time, recurring task interval, delayed task time and duration of the new system task schedule directory.

[0081] In one embodiment, the task scheduling binding unit includes:

[0082] The unit is used to call the get_Actions function in the ITaskDefinition structure to obtain the IActionCollection structure;

[0083] The calling unit is used to call the get_Count function in the IActionCollection structure to obtain the number of activities in the system task plan;

[0084] The traversal unit is used to traverse the IAction structure in the IActionCollection structure according to the number of activities in the system task plan, and call the get_Item function in the IActionCollection structure to obtain the IAction structure;

[0085] The judgment unit is used to determine whether the class identifier exists in the IAction structure; if it does not exist, the class identifier is bound to the system task plan; if it exists, success is returned directly.

[0086] In one embodiment, the task scheduling binding unit further includes:

[0087] The startup unit is used to obtain the IComHandlerAction structure through the QueryInterface function in the IAction structure;

[0088] The specified unit is used to call the Create function in the IActionCollection structure to specify the IAction structure in order to create a new IAction structure;

[0089] The binding unit is used to call the QueryInterface function in the new IAction structure to bind the IComHandlerAction structure;

[0090] The output unit is used to call the put_ClassId function in the IComHandlerAction structure to specify the class identifier.

[0091] Since the embodiments of the apparatus and the embodiments of the method correspond to each other, please refer to the description of the embodiments of the method for the embodiments of the apparatus, which will not be repeated here.

[0092] This invention also provides a computer-readable storage medium storing a computer program thereon, which, when executed, can perform the steps provided in the above embodiments. The storage medium may include various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0093] This invention also provides a computer device, which may include a memory and a processor. The memory stores a computer program, and when the processor calls the computer program in the memory, it can implement the steps provided in the above embodiments. Of course, the computer device may also include various network interfaces, power supplies, and other components.

[0094] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the systems disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the descriptions are relatively simple; relevant parts can be referred to in the method section. It should be noted that those skilled in the art can make various improvements and modifications to this application without departing from the principles of this application, and these improvements and modifications also fall within the protection scope of the claims of this application.

[0095] It should also be noted that, in this specification, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

Claims

1. A method for unconventional automatic startup of system task schedulers based on Windows, characterized in that, include: Locate the system task plan and extract the system task plan to obtain system task plan data; wherein, the system task plan data includes a system task plan directory; Based on the system task plan data, construct the DLL module and system task plan parameters respectively; and register the DLL module as a COM component and generate a class identifier; Check if the system task schedule directory exists; if it does not exist, create a new system task schedule directory and reset the trigger; if it exists, do not reset the trigger; wherein, the trigger is used to set the attributes of the system task schedule. Add the system task plan parameters to the system task plan, and bind the class identifier to the system task plan; Save the system task schedule to the system task schedule directory, set the highest privileges, and use the highest privileges to enable the unconventional auto-start of the system task schedule.

2. The Windows-based system task scheduling non-conventional auto-start method according to claim 1, characterized in that, The system task plan data also includes: system task plan name, trigger start frequency, operation attributes, and condition attributes.

3. The Windows-based system task scheduling non-conventional auto-start method according to claim 1, characterized in that, The step of constructing the DLL module and system task plan parameters based on the system task plan data includes: Export the functions DllGetClassObject, DllCanUnloadNow, DllRegisterServer, and DllUnregisterServer respectively; Construct the directory location and name of the system task plan respectively; Construct the full path where the DLL module is stored.

4. The Windows-based system task scheduling non-conventional auto-start method according to claim 3, characterized in that, The step of registering the DLL module as a COM component and generating a class identifier includes: Register the DLL module as the COM component using the Regsvr32 command based on the full path; The generated class identifier is obtained based on the COM component.

5. The Windows-based system task scheduling non-conventional auto-start method according to claim 1, characterized in that, The step of creating a new system task schedule directory and resetting triggers includes: Set the startup, creation, or modification time, recurring task interval, delayed task time, and duration for the new system task schedule directory.

6. The Windows-based system task scheduling non-conventional auto-start method according to claim 1, characterized in that, Adding the system task schedule parameters to the system task schedule and binding the class identifier to the system task schedule includes: Call the get_Actions function in the ITaskDefinition structure to obtain the IActionCollection structure; Call the get_Count function in the IActionCollection structure to obtain the number of activities in the system task plan; Based on the number of activities in the system task plan, traverse the IAction structures in the IActionCollection structure and call the get_Item function in the IActionCollection structure to obtain the IAction structure; Determine whether the class identifier exists in the IAction structure; if it does not exist, bind the class identifier to the system task schedule; if it exists, return success directly.

7. The Windows-based system task scheduling non-conventional auto-start method according to claim 6, characterized in that, The step of adding the system task plan parameters to the system task plan and binding the class identifier to the system task plan further includes: The IComHandlerAction structure is obtained through the QueryInterface function in the IAction structure; Call the Create function in the IActionCollection structure to specify the IAction structure and create a new IAction structure; Call the QueryInterface function in the new IAction structure to bind the IComHandlerAction structure; The class identifier is specified by calling the put_ClassId function in the IComHandlerAction structure.

8. A non-conventional auto-start device for Windows-based system task scheduling, characterized in that, include: The task plan acquisition unit is used to locate system task plans and extract the system task plans to obtain system task plan data; wherein, the system task plan data includes a system task plan directory; The task plan construction unit is used to construct a DLL module and system task plan parameters according to the system task plan data; and to register the DLL module as a COM component and generate a class identifier. A task schedule detection unit is used to detect whether the system task schedule directory exists; if it does not exist, a new system task schedule directory is created and the trigger is reset; if it exists, the trigger is not reset; wherein, the trigger is used to set the attributes of the system task schedule. A task plan binding unit is used to add the system task plan parameters to the system task plan and bind the class identifier to the system task plan; The task schedule startup unit is used to save the system task schedule to the system task schedule directory, set the highest privileges, and use the highest privileges to realize the unconventional self-start of the system task schedule.

9. A computer device, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the Windows-based system task scheduling unconventional self-starting method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the Windows-based system task scheduling unconventional self-starting method as described in any one of claims 1 to 7.

Images