WO2017173925A1

WO2017173925A1 - Software management method and device, terminal, and storage medium

Info

Publication number: WO2017173925A1
Application number: PCT/CN2017/077869
Authority: WO
Inventors: 孟凡龙
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-04-06
Filing date: 2017-03-23
Publication date: 2017-10-12
Also published as: CN107273145A

Abstract

A software management method and device, terminal, and storage medium. The method comprises: acquiring information of software, and starting to execute management operation on the software (S101); performing, during the management operation, system window monitoring (S102); upon detecting generation of a new window, identifying the window type of the new window (S103); matching the window type of the new window against a predetermined window handling rule (S104), wherein the predetermined window handling rule defines a handling mode for each window type; and after the matching result is obtained, handling, according to the matching result, the new window to complete the management operation on the software (S105).

Description

Software management method and device, terminal and storage medium

Technical field

The present invention relates to the field of software, and in particular, to a software management method and apparatus, a terminal, and a storage medium.

Background technique

With the continuous development of the Internet technology (IT) field and the terminal industry, more and more software applications, more and more software, more and more choices of users, so it is necessary to enhance their competitiveness. Need to do their own products better, so in order to improve the user experience, more and more methods of automatic software installation or uninstallation are provided.

In the prior art, there is a fully automatic installation software technology that utilizes the file shell identification technology to extract the silent parameters of the installation program. Through the silent installation mode, the unknown window appearing during the installation process can be effectively avoided, which is to apply all the application software. The installation process is simplified to a single command. You don't need to click the mouse to select other installation operations such as “Next”, and you don't need to type the keyboard to enter the installation path. However, not all software can be installed using the silent installation mode. In fact, only a small percentage of the software supports the silent installation mode. Therefore, this automated installation method is not universal. In addition, in the prior art, there is also an automatic installation technology, which uses a script to simulate a mouse, a keyboard, and the like to complete the software installation. Since the process of recording a keyboard and a mouse is required, the first time the application is installed, it must be manually operated. At the same time, because the pop-up window is not static during the software installation process, the script recording needs to include all pop-up windows during the software installation process, which is relatively difficult and generally low. In order to solve the problem of universality, there is another general software installation method in the prior art, which realizes the installation of the application by intelligently simulating the method of manually clicking the interface by analyzing the installation software. However, in actual application, the software is installed. During the installation of the program, an interface that does not belong to the installation process may appear. For example, the system pops up, which causes softness. The piece cannot be installed.

In summary, although there are automatic software installation methods in the prior art, these software installation methods are generally less universal and have no universality due to limitations of their own reasons; or they are susceptible to other pop-up windows during the installation process. Unable to continue the installation.

Summary of the invention

The embodiment of the invention provides a software management method and device, a terminal and a storage medium, which solve the problem that the versatility and the other windows are not affected in the process of automatically installing or uninstalling the software in the prior art.

To solve the above technical problem, an embodiment of the present invention provides a software management method, including:

Obtaining software information and starting to perform management operations on the software;

Monitoring the system window during the management operation; when a new window is generated on the monitoring system interface, identifying the window type of the new window, and matching the window type with the preset window processing rule, wherein the pre- Setting a window processing rule to define a processing method corresponding to each window type;

The new window is processed according to the matching result, and the management operation of the software is completed.

In an embodiment of the present invention, the window type includes an application window type and an abnormal window type; the preset window processing rule includes:

When the window type belongs to the application window type, acquiring control information of the window, and performing operation control on the content of the control;

When the window type belongs to the exception window type, the window is closed.

In an embodiment of the present invention, before acquiring the software information, the method further includes: setting an abnormal window set, where the abnormal window set includes all window identifiers belonging to the abnormal window type window;

Identifying the window type of the new window includes: obtaining a window identifier of the new window, and determining whether the new window belongs to the abnormal window set, and if yes, the window type of the new window is an abnormal window type.

In an embodiment of the present invention, after performing the management operation on the software, before identifying the window type of the new window, the method further includes: acquiring a process identifier of the software;

Identifying a window type of the new window includes obtaining a process identifier of the new window, determining whether a process identifier of the new window is consistent with a process identifier of the software, and if so, a window type of the new window is Application window type.

In an embodiment of the invention, performing a management operation on the software includes performing an installation or uninstallation of the software.

In an embodiment of the present invention, when the management of the software is performed to perform the uninstallation of the software, after the uninstalling of the software is completed, the method further includes: querying whether the software is still in the registry. Relevant information, if yes, repeating the step of uninstalling the software or deleting related information of the software in the registry.

An embodiment of the present invention further provides a software management apparatus, including: an operation module configured to acquire software information, and start to perform a management operation on the software;

Window processing module: configured to monitor a system window during a management operation; when a new window is generated on the monitored system interface, identify a window type of the new window, and match the window type with a preset window processing rule The preset window processing rule defines a processing manner corresponding to each window type;

The execution module is configured to process the new window according to the matching result, and complete management operations on the software.

In an embodiment of the present invention, the method further includes: setting a module: configured to acquire software information Pre-setting an exception window set, the exception window set including all window identifiers belonging to the exception window type window;

The window processing module further includes a first identification sub-module configured to acquire a window identifier of the new window, and determine whether the new window belongs to the abnormal window set, and if yes, the window type of the new window is abnormal Window type.

In an embodiment of the present invention, the method further includes: acquiring, configured to acquire a process identifier of the software before identifying a window type of the new window after performing a management operation on the software;

The window processing module further includes a second identification submodule configured to acquire a process identifier of the new window, determine whether a process identifier of the new window is consistent with a process identifier of the software, and if so, The window type of the new window is the application window type.

In an embodiment of the present invention, the method further includes: a reprocessing module configured to query the registry after performing the uninstallation of the software after performing the uninstallation of the software by the management operation of the software Whether there is the software related information, and if so, repeating the step of uninstalling the software or deleting related information of the software in the registry.

An embodiment of the present invention further provides a terminal, including the foregoing software management apparatus.

The embodiment of the invention provides a computer storage medium, wherein the computer storage medium stores computer executable instructions configured to execute the software management method provided above.

The embodiment of the invention further provides a terminal, comprising: a processor and a storage medium configured to store executable instructions, wherein the processor is configured to execute the stored executable instructions, the executable instructions comprising:

Monitoring a system window during a management operation; when a new window is generated on the monitored system interface, identifying a window type of the new window, and matching the window type with a preset window processing rule, the preset window The processing rule defines the processing method corresponding to each window type;

The beneficial effects of the embodiments of the present invention are:

The embodiment of the invention provides a software management method and device, a terminal, a storage medium, acquires software information, and starts to perform management operations on the software; monitors a system window during a management operation, and when a new window is detected And identifying a window type of the new window, and matching the window type of the new window with a preset window processing rule, wherein the preset window processing rule defines a processing manner corresponding to each window type, and after matching the result According to the matching result, the new window is processed to complete the management operation of the software. In the process of software management operations, the system window is monitored, and different processing methods are adopted according to the monitored window, because most software installation and uninstallation can be performed according to the above process, so it is universal; The software management method in the present invention adopts different processing manners for different types of windows, and can effectively avoid the situation that the system pop-up window causes the installation process to be blocked. Therefore, the problem that the versatility and the influence of other windows cannot be considered in the automatic installation or uninstallation process of the software existing in the prior art can be effectively solved; the versatility of the software management is increased, and the other windows are not affected, thereby improving the user. The effect of the experience.

DRAWINGS

1 is a flowchart of a software management method according to Embodiment 1 of the present invention;

2 is a flowchart of a software installation method in Embodiment 1 of the present invention;

3 is a flowchart of a software uninstalling method according to Embodiment 1 of the present invention;

4 is a schematic structural diagram of a software management apparatus according to Embodiment 2 of the present invention.

detailed description

The present invention will be further described in detail below with reference to the accompanying drawings.

Embodiment 1:

This embodiment provides a software management method. Referring to FIG. 1, the method includes:

S101: Acquire software information, and start to perform management operations on the software;

S102: monitor a system window during a management operation;

S103: when a new window is generated on the monitored system interface, identify a window type of the new window;

S104: Match the window type with a preset window processing rule.

S105: Process the new window according to the matching result, and complete a management operation on the software.

To perform management control on the software, first obtain information about the software, and perform step S101. In this embodiment, the management operation may be to install or uninstall the software, or to install the software first, and then based on the installed The software is uninstalled. If the management operation is software installation, the acquired software information includes the software installation package information. For example, the installation package of the possible software is downloaded from the network and is in the form of a compressed package. In order to complete the installation of the software, the installation package must be first decompressed, and the decompressed information is not required to be executed. . If so, obtain the installation software that needs to be executed, and the software information is the installation software. For software uninstallation, you need to get the information of the software that needs to be uninstalled first. For example, when you want to uninstall a software A, you can scan the registry information and match the content of the "DisplayName" item in the registry according to the name of the software A to obtain the information that needs to be uninstalled. After the related information of the software is obtained, the corresponding operations need to be performed. In this embodiment, the software installation or software uninstallation is mainly included. The specific triggering method can be a simple click to start the installation or software uninstallation. The above examples are merely illustrative of specific examples and are not intended to limit the scope of the embodiments.

After the management operation of the software is started, step S102 is performed, the system window is monitored during the management operation, and the system window changes during the execution of the software management operation (that is, installation or uninstallation), possibly Some windows will be added, and the system window will be monitored for software automation to perform the next installation. Then, step S103 is executed. When a new window is generated on the system interface, the new window is identified, mainly to identify the window type of the new window. It is easy to understand that during the installation process, the software is usually installed or uninstalled to install or uninstall the window interface to facilitate interaction with the user. The software is used to interact with the user, and those window types of the correctly installed window are defined as application windows. Types of. Of course, there are often other windows popping up during the installation or uninstallation process. These windows may be system reminders, for example, the system pops up, prompting that the registry key has been changed. For such windows, define it as an exception window type.

In a specific implementation manner of this embodiment, an abnormal window set is further set before the step S101 is performed, and the abnormal window set includes all window identifiers belonging to the abnormal window type window. For example, the exception window set includes: "Program Compatibility Assistant", "Windows Security Alert", "Desktop Gadget - Security Warning", and so on. In the case that the abnormal window set is set in advance, to complete the recognition of the window type of the new window, only the window identifier of the new window needs to be acquired, and it is determined that the acquired new window identifier is an identifier that does not belong to the abnormal window set. For example, a new window is generated on the monitoring system interface, the window identifier of the new window is obtained as “Windows security alarm”, and then the abnormal window set is viewed, and the abnormal window set is found to contain “Windows security alarm”, so that it can be known that The new window belongs to the exception window. In this way, the window of the abnormal window type can be easily identified. This process can use the Windows API functions EnumWindows, GetWindowText to enumerate all the top-level window identifiers on the screen.

In another specific implementation manner of this embodiment, after performing step S101, a process IDentifier (PID) of the software is also acquired, and the PID is a kernel used by most operating systems to uniquely identify the process. Value. In this case, the window can be identified. By obtaining the PID of the new window, it is obvious whether the PID of the new window is consistent with the PID of the software. If it is consistent, it is obvious that the new window is the window in which the software itself runs. In this way, the window of the application window type can be easily identified.

In the above embodiment, two different ways are used to identify different types of windows. In fact, when the new window does not belong to the abnormal window type, the new window can be roughly determined as the application window type, but this is in the user. There is no operation of any other software or no other window with a non-exceptional window type. For example, when a user automatically installs a certain software, other software can be opened to perform other operations, so the determination in this way is inaccurate. Moreover, it is convenient and accurate to use PID to judge. Therefore, it is a preferable way to recognize the window of the abnormal window type with the abnormal window set and the window of the application window type by using the PID.

After the window type of the new window is recognized, step S104 is performed to match the window type of the new window with the preset processing rule. In the preset processing rule, a corresponding processing method for each window type is defined. For example, specifically, when the window type belongs to the application window type, the control information of the window is acquired, and the content of the control is controlled; when the window type belongs to the abnormal window type, the window is closed. When the window type is abnormal window type, it is proved that the window is not the window required to perform software management operations, and may hinder the normal operation of the software management operation, so the more direct way is to turn it off, the shutdown mode may be Close the corresponding process. When the window type is the application window type, it is proved that the window belongs to the object of the management operation, so it is necessary to acquire the information of each control of the window and perform operation control on the content of the control. Since the types of windows that are of interest in the present invention are mainly the exception window type and the application window type, no description is made for other window types. In addition, the specific content of the preset processing rule is not limited to the above setting manner.

The processing mode for different types of windows has been defined in the preset processing rule, and only corresponding processing is performed according to the matching result, and the process proceeds to step S105. If the new window type is The exception window type closes the new window; if it is the application window type, the control information of the window is obtained, and the content of the control is controlled. Since the management operations in this embodiment mainly include installation and uninstallation, the control information obtained in the window here mainly includes acquiring mouse button operable buttons and an edit box for inputting text. This process mainly uses the Windows API function EnumChildWindows to enumerate the control types and control texts on the installation interface, such as Edit, CButton, Static, etc. After finding the button type controls, you can analyze the text content of these controls, such as controls. Keywords such as "ChooseInstallLocation" and "SelectDestinationLocation" in the text indicate that this window belongs to the modified software installation path interface and sends a message through the Application Programming Interface (API). SendMessage) sends the path to the specified control to complete the modification path; if the control text contains keywords such as "I have read and accept permission", "Next", "End", "Complete", etc., it means that it belongs to the normal installation selection interface. Then send a mouse click message through API SendMessage to simulate a manual click operation. Of course, if it is an exception window type window, close it. For example, this procedure can use the Windows API functions EnumWindows and GetWindowText to enumerate all the top-level window identifiers on the screen. When the window identifier matches the window identifier in the exception window set in the configuration file, Use the API function FindWindow to get the window handle, and finally use GetWindowThreadProcessId, TerminateProcess to end the window process.

In this embodiment, in order to facilitate more convenient acquisition of software related information when uninstalling the software, in a specific embodiment of the present invention, all disk sizes and specific registries are also scanned before the installation of the software is performed. Item and record it in a temporary file. And after executing the installation of the software, it will scan all the disk sizes and specific registry entries for the second time, so that you can know the specific installation location of all the files of the software, related registry keys, the size of the software, and so on. information. In this way, on the one hand, it can be determined whether the software installation is successful, on the other hand, it can be easily uninstalled. According to the specific installation location of all files of the software at the time of uninstallation, relevant registry entries, The specific information such as the size of the space occupied by the software can know the specific programs and parameters that need to be uninstalled, so that it can be completely uninstalled. In addition, the software uninstallation process can be judged after the software uninstallation process is completed, and the software uninstallation is successful. If the uninstallation is successful, the uninstallation process can be re-executed. Of course, the unsuccessful uninstallation may also include that the related information is not uninstalled cleanly, for example, the registry information is not deleted, and only the registry information needs to be deleted at this time.

Referring to FIG. 2, a specific implementation manner of installing software in this embodiment includes:

S201: application software package analysis;

The analysis of the software package is the basis of the entire business process. If it is in the form of a compressed package, it needs to be decompressed first. Extract to a temporary subdirectory.

S202: Scan an application software directory;

Find out if there is a Windows installation package. If there is a Windows installation package, that is, the software to be installed already exists in the current system; warning information will be displayed, and maintenance personnel can interrupt the subsequent processing.

S203: The first disk scan and the registry record the existing disk size and the installation software already in the registry.

Scans the value of "DisplayName" in the "SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall" registry key for all subkeys via the HKEY_LOCAL_MACHINE entry and HKEY_USERS. And recorded in a temporary file.

S204: Start a system window monitoring thread;

During the software installation process, an exception window type window may appear, which can be processed through the configuration file configuration window identifier, such as the window identifiers "Program Compatibility Assistant", "Windows Security Alert", "Desktop Gadget - Security Warning", and IE browser pop-ups, etc. This process mainly uses the Windows API functions EnumWindows and GetWindowText to enumerate the top-level window titles on all screens. If the window identifier matches the identifier text to be processed in the configuration file, use the API function FindWindow to get the window handle, and finally use GetWindowThreadProcessId, TerminateProcess end window process.

S205: Obtain a PID related to the installation software, and determine whether there is a child process, if yes, prove that the software installation is being executed, then execute S206; otherwise, execute S211;

S206: Scan the window handle of all visible windows, and obtain the PID by the handle;

S207: Select a visible window in which the PID is consistent with the PID of the software, and obtain control information of the window;

The control information includes a mouse-operable button control and an edit box for inputting text. The default installation path can be replaced during the installation process, mainly by analyzing the text information or button information in the window. This process mainly uses the Windows API function EnumChildWindows to enumerate the control types and control texts on the installation interface, such as Edit, CButton, Static, etc. After finding the button type controls, you can analyze the text content of these controls, such as controls. The text contains keywords such as "Choose Install Location", "Select Installation Location", and "Select Destination Location", indicating that this window belongs to the modified software installation path interface, and sends the path to the specified control through the API SendMessage to complete the modification path; The control text contains keywords such as "I have read and accept permission", "Next", "End", "Complete", etc., indicating that it belongs to the normal installation selection interface, and then sends a mouse click message through API SendMessage to simulate manual click. operating.

S208: Perform a second disk and registry scan.

Calculate the size of the disk change, compare the changes in the registry after the first scan and the second scan, and get the software installation list.

S209: Determine, according to the installation list, whether the software installation is successful, and if yes, proceed to S211; otherwise, execute S210.

S210: Select whether to re-install, if yes, execute 201 again; otherwise, go to S211.

S211: End the installation process.

Referring to FIG. 3, a specific implementation manner of uninstalling software in this embodiment includes:

S301: According to the software installation list obtained by scanning the registry during the software installation process.

Match the "DisplayName" in the registry key according to the software name, and get the value of "UninstallString", that is, software uninstallation.

S302: Run the software uninstall command corresponding to “UninstallString” to start the uninstaller.

S303: Start a system window monitoring thread.

The monitoring process and the window processing of the exception window type are similar to those in S204.

S304: Acquire a PID related to the installation software, and determine whether there is a child process. If yes, if it is proved that the software uninstallation is being executed, execute S305; otherwise, execute S309.

S305: Scan the window handle of all visible windows, and get the PID by the handle.

S306: Select a visible window in which the PID is consistent with the PID of the software, and obtain control information of the window.

Get the control information of the window, you can simulate the manual uninstall application software. This process uses the Windows API functions such as EnumWindows, FindWindow, GetWindowThreadProcessId, etc. to analyze the uninstall window of the currently visible window belonging to the installation process ID. If there is a visible window, use EnumChildWindows, GetWindowRect The GetWindowText function enumerates the text, position, and other information of all controls in the window. For example, the text of the control on the installation interface is "uninstall", "delete", "remove", "uninstall", and so on. Then use SendMessage to send a mouse click message to complete the interface operation.

S307: Determine whether the software uninstallation is successful, and if yes, go to S309; otherwise, execute S308.

S308: Select whether to perform the uninstallation again, if yes, re-execute 301; otherwise, enter S309.

S309: End the uninstallation process.

The above examples are only illustrative of the solution of the present invention, and do not impose any limitation on the solution of the present invention. By adopting the management method of the invention, the automatic installation and uninstallation of the software can be completed, and the problem of installation or uninstallation interruption caused by the abnormal window can be well avoided, and the user body is improved. Test.

Embodiment 2:

In this embodiment, a software management apparatus is further provided. Referring to FIG. 4, the software management apparatus 4 includes: an operation module 41, a window processing module 42, and an execution module 43. The operation module 41 is configured to acquire software information, and start executing the opposite. The management operation of the software; the window processing module 42 is configured to monitor the system window during the management operation; when a new window is generated on the monitored system interface, the window type of the new window is recognized, and the window type and the preset window processing rule are Performing matching, wherein the preset window processing rule defines a processing manner corresponding to each window type; the executing module 43 is configured to process the new window according to the matching result, and complete a management operation on the software.

The window type includes an application window type and an exception window type; the preset window processing rule includes: when the window type belongs to the application window type, the execution module 43 is configured to acquire the control information of the window, and perform operation control on the content of the control; when the window type belongs to When the exception window type is closed, the window is closed. The software management apparatus 4 further includes a setting module 44 configured to pre-set an exception window set including all window identifiers belonging to the abnormal window type window before acquiring the software information. The window processing module 42 further includes a first identification sub-module 421 configured to acquire a window identifier of the new window, and determine whether the new window belongs to the abnormal window set, and if so, the window type of the new window is an abnormal window type.

The software management apparatus 4 further includes an acquisition module 45 configured to acquire a process identifier of the software before identifying a window type of the new window after performing a management operation on the software; the window processing module 42 further includes a second identification sub-module 422, Configured to obtain the process identifier of the new window, determine whether the process identifier of the new window is consistent with the process identifier of the software, and if so, the window type of the new window is the application window type. Performing management operations on the software includes performing an installation or uninstallation of the software.

Also included is a reprocessing module 46 configured to perform a management operation on the software to perform the When the uninstallation of the software is completed, after the uninstallation of the software is completed, whether the software related information is still in the registry is queried, and if so, the step of uninstalling the software is repeated or the related information of the software in the registry is deleted. The software management apparatus in this embodiment may be configured to execute the software management method in the first embodiment.

A terminal is also provided in this embodiment, and the terminal may include, but is not limited to, a notebook computer, a desktop computer, a mobile terminal, and the like. The terminal includes the software management device in this embodiment, and can be configured to manage the software and execute the software management method in the first embodiment.

Each module included in the software management apparatus and each submodule included in each module in the embodiment of the present invention may be implemented by a processor in a terminal (for example, a computer), and may also be implemented by a logic circuit; In the process, the processor may be a central processing unit (CPU), a microprocessor (MPU), a digital signal processor (DSP), or a field programmable gate array (FPGA).

It should be noted that, in the embodiment of the present invention, if the software management method described above is implemented in the form of a software function module and sold or used as a stand-alone product, it may also be stored in a computer readable storage medium. Based on such understanding, the technical solution of the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product stored in a storage medium, including a plurality of instructions. A computer device (which may be a personal computer, server, or network device, etc.) is caused to perform all or part of the methods described in various embodiments of the present invention. The foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read only memory (ROM), a magnetic disk, or an optical disk. Thus, embodiments of the invention are not limited to any specific combination of hardware and software.

Correspondingly, an embodiment of the present invention provides a computer storage medium, where the computer storage medium stores computer executable instructions, and the computer executable instructions are configured to execute the software management method provided above.

Correspondingly, an embodiment of the present invention further provides a terminal, including: a processor and a storage medium configured to store executable instructions, where the processor is configured to execute the stored executable instructions, where the executable instructions include:

The above examples are only illustrative of the solution of the present invention, and do not impose any limitation on the solution of the present invention. With the software management device in this embodiment, the problem of installation or uninstallation interruption caused by the abnormal window can be well avoided, and the uninstallation or installation process is automatically executed by the software management device, thereby improving the user experience.

Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in a storage medium (ROM/RAM, diskette, optical disk) by a computing device, and in some cases The steps shown or described may be performed in an order different than that herein, or they may be separately fabricated into individual integrated circuit modules, or a plurality of the modules or steps may be implemented as a single integrated circuit module. Therefore, the invention is not limited to any particular combination of hardware and software.

The above is a further detailed description of the present invention in connection with the specific embodiments, and the specific embodiments of the present invention are not limited to the description. It will be apparent to those skilled in the art that the present invention may be made without departing from the spirit and scope of the invention.

Industrial applicability

In the process of software management operations, the system window is monitored, and different processing methods are adopted according to the monitored window, because most software installation and uninstallation can be performed according to the above process, so it is universal; The software management method in the present invention adopts different processing manners for different types of windows, and can effectively avoid the situation that the system pop-up window causes the installation process to be blocked. Therefore, the problem that the versatility and the influence of other windows cannot be considered in the automatic installation or uninstallation process of the software existing in the prior art can be effectively solved; the versatility of the software management is increased, and the other windows are not affected, thereby improving the user. The effect of the experience.

Claims

A software management method comprising:

Obtaining software information and starting to perform management operations on the software;

Monitor system windows during management operations;

When a new window is generated on the monitoring system interface, the window type of the new window is identified, and the window type is matched with a preset window processing rule, wherein the preset window processing rule defines a processing corresponding to each window type. the way;

The new window is processed according to the matching result, and the management operation of the software is completed.
The software management method according to claim 1, wherein the window type comprises an application window type and an exception window type; and the preset window processing rule comprises:

When the window type belongs to the application window type, acquiring control information of the window, and performing operation control on the content of the control;

When the window type belongs to the exception window type, the window is closed.
The software management method according to claim 2, further comprising: presetting an abnormal window set, wherein the abnormal window set includes all window identifiers belonging to the abnormal window type window;

Identifying the window type of the new window includes: obtaining a window identifier of the new window, and determining whether the new window belongs to the abnormal window set, and if yes, the window type of the new window is an abnormal window type.
The software management method according to claim 2, wherein after the management operation of the software is performed, before identifying the window type of the new window, the method further comprises:

Obtaining a process identifier of the software;

Identifying a window type of the new window includes: obtaining a process identifier of the new window, determining whether a process identifier of the new window is consistent with a process identifier of the software, and if so, a window type of the new window For the application window type.
A software management method according to any one of claims 1 to 4, wherein performing a management operation on the software comprises performing an installation or uninstallation of the software.
The software management method according to claim 5, wherein when performing the management operation of the software to perform the uninstallation of the software, after completing the uninstalling of the software, the method further comprises: querying whether the registry is still There is the software related information, and if so, repeating the step of uninstalling the software or deleting related information of the software in the registry.
A software management device comprising:

An operation module: configured to acquire software information, and start to perform management operations on the software;

Window processing module: configured to monitor a system window during a management operation; when a new window is generated on the monitored system interface, identify a window type of the new window, and match the window type with a preset window processing rule The preset window processing rule defines a processing manner corresponding to each window type;

The execution module is configured to process the new window according to the matching result, and complete management operations on the software.
The software management apparatus according to claim 7, wherein the window type includes an application window type and an abnormal window type; and the preset window processing rule comprises:

When the window type belongs to the application window type, acquiring control information of the window, and performing operation control on the content of the control;

When the window type belongs to the exception window type, the window is closed.
The software management apparatus according to claim 8, further comprising: a setting module configured to preset an abnormal window set before acquiring the software information, the abnormal window set including all window identifiers belonging to the abnormal window type window;

The window processing module further includes a first identification submodule configured to acquire a window identifier of the new window, and determine whether the new window belongs to the abnormal window set, and if so, the The window type of the new window is the exception window type.
The software management apparatus according to claim 8, further comprising an acquisition module configured to acquire a process identifier of said software before identifying a window type of said new window after performing a management operation on said software ;

The window processing module further includes a second identification submodule configured to acquire a process identifier of the new window, determine whether a process identifier of the new window is consistent with a process identifier of the software, and if so, The window type of the new window is the application window type.
A software management apparatus according to any one of claims 7 to 10, wherein performing a management operation on the software comprises performing an installation or uninstallation of the software.
The software management apparatus according to claim 11, further comprising a reprocessing module configured to, after performing an operation of the software to perform uninstallation of the software, after completing uninstallation of the software, Query whether there is any software related information in the registry, and if so, repeat the step of uninstalling the software or delete related information of the software in the registry.
A terminal comprising the software management apparatus according to any one of claims 7-12.
A computer storage medium having stored therein computer executable instructions configured to perform the software management method of any of claims 1-6.
A terminal comprising: a processor and a storage medium configured to store executable instructions, wherein the processor is configured to execute the stored executable instructions, the executable instructions comprising:

Obtaining software information, and starting to perform management operations on the software; monitoring a system window during a management operation; and when a new window is generated on the monitored system interface, identifying a window type of the new window, the window is The type is matched with a preset window processing rule, and the preset window processing rule defines a processing manner corresponding to each window type; the new window is processed according to the matching result, and the management operation of the software is completed.